Atsuko, I am so sorry I didn't take the time to run it through the compiler. This was an oversight on my part. I had removed the dependencies on the ogf_nsi_connection_faults_1_0.wsdl file but forgot to remove the imports. It just happened to pass validation since I left the fault file in my local directory :-( I have removed the associated imports and compiled the WSDL. The updated versions are attached. I will send a separate response on the asynchronous topic. 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