I resend the reply message because I failed to post to the NSI mailing list. ---------- Forwarded message ---------- From: Atsuko Takefusa <atsuko.takefusa@aist.go.jp> Date: 2011/4/27 Subject: Re: [Nsi-wg] Updated NSI Connection Services Schema To: John MacAuley <john.macauley@surfnet.nl> Cc: nsi-wg@ogf.org Hi John, Thank you for sending us the updated wsdls. I will check them. I did not know implementation of the JAX-WS asynchronous invocation model at that time. But now, I want to use this model, as a developer. :) Thanks, Atsuko 2011/4/27 John MacAuley <john.macauley@surfnet.nl>:
Atsuko, You are correct in that the JAX-WS 2.0 asynchronous invocation model is an elegant solution and it can be used on the existing synchronous WSDL definition by annotating the service definition binding with "<enableAsyncMapping>true</enableAsyncMapping>". This will let you utilize the JAX-WS asynchronous interface with the existing synchronous WSDL message interaction. Can I assume you want to take this one step further and use the WS-Addressing asynchronous message exchange? For those in Hong Kong you may remember be discussing WS-Addressing in one of the presentations. I had thought about using it, but I was concerned implementation compatibility, and peoples willingness to move away from the synchronous pattern. This was why I simulated a similar mechanism using the synchronous model, and putting the replyTo address and a transactionId in the message specification. I am open to revisiting the topic as it will only change the WSDL specific files. John. On 2011-04-26, at 3:32 AM, Atsuko Takefusa wrote:
Hi all,
Jouh, could you send us "ogf_nsi_connection_faults_1_0.wsdl", please? I cannot generate stub files.
By the way, it might be too late,,, I have investigated on web services asyncronous call and I thought why we would not use the JAX-WS asynchronous invocation model. General WS development tools, such as Axis and CXF, support this model, which enables us to develop client and server codes easily and beautifully.
Thanks,
Atsuko G-lambda, AIST
2011/4/25 John MacAuley <john.macauley@surfnet.nl>:
Found a small error this morning when updating the reserveRequest XML instance. Have attached all the files again.
John.
On 2011-04-24, at 11:37 PM, John MacAuley wrote:
I have attached an update XSD and both the interface and service WSDL. Please have a look at these new versions as there are some changes.
John.
<ogf_nsi_connection_interface_1_0.wsdl><ogf_nsi_connection_service_1_0.wsdl><ogf_nsi_connection_types_1_0.xsd>_______________________________________________
nsi-wg mailing list
nsi-wg@ogf.org
http://www.ogf.org/mailman/listinfo/nsi-wg
_______________________________________________
nsi-wg mailing list
nsi-wg@ogf.org
http://www.ogf.org/mailman/listinfo/nsi-wg
-- Atsuko Takefusa Information Technology Research Institute, AIST
-- Atsuko Takefusa, Ph. D. Information Technology Research Institute, AIST -- Atsuko Takefusa Information Technology Research Institute, AIST