8 | | As there are no available generalized standards for such an interface, we are free to define one. One solution is to use the soaplab async. interface, which is [http://soaplab.sourceforge.net/soaplab1/images/soaplab-api.jpg described in the soaplab documentation]. For WSDL-described services it would be useful if it were defined in a WSDL file, which should be reused as much as possible, and then imported into the WSDL of the service you wish to provide a async interface to ([attachment:wiki:AsynchronousServicesFifth:sayHello.wsdl see example below]). |
| 8 | As there are no available generalized standards for such an interface, we are free to define one. One solution is to use the soaplab async. interface, which is [http://soaplab.sourceforge.net/soaplab1/images/soaplab-api.jpg described in the soaplab documentation]. For WSDL-described services it would be useful if it were defined in a WSDL file, which should be reused as much as possible, and then imported into the WSDL of the service you wish to provide a async interface to ([attachment:wiki:AsynchronousServicesFifth:sayHello.wsdl see example below]). WSDL 2.0 helps a lot in this area. |
| 9 | |
| 10 | * [http://www.ibm.com/developerworks/webservices/library/ws-rest1/ REST and Web Services in WSDL 2.0] |