Asynchronous web services
Hi, I have a question about Asynchronous web services. Can a Web Service client use asynchronous style when the Web Service server is using synchronous style? Here's an example: I have a Web Service that is developed to work in a synchronous style (generated the server side code using WSDL2Java with -s option). Can I create the Web Service client to work in asynchronous style (generate the client side code using WSDL2Java with -a option)? Thanks Raghu
Re: Asynchronous web services
Yes you can do it that way. Thanks, Keith. On Sat, Sep 27, 2008 at 2:20 AM, Raghu Upadhyayula [EMAIL PROTECTED] wrote: Hi, I have a question about Asynchronous web services. Can a Web Service client use asynchronous style when the Web Service server is using synchronous style? Here's an example: I have a Web Service that is developed to work in a synchronous style (generated the server side code using WSDL2Java with -s option). Can I create the Web Service client to work in asynchronous style (generate the client side code using WSDL2Java with -a option)? Thanks Raghu -- Keith Chapman Senior Software Engineer WSO2 Inc. Oxygenating the Web Service Platform. http://wso2.org/ blog: http://www.keith-chapman.org
Asynchronous web services using Axis2 with XMLBeans binding
I am developing asynchronous web services using Axis2 with XMLBeans binding. 1)We are using this command to generate the client stubs WSDL2Java -uri ABC.wsdl -d xmlbeans -a 2)When calling stub's startxyz() method through our Client Program for asynchronous calling of our web service, the request is not going to server side and it is not showing any client side exception. 3)But when we change _operationClient.execute(true); line in startxyz() method of the client stub which was earlier _operationClient.execute(false); the request went to server side. Axis 1.4 version is used There is one solution to it. Putting Thread.sleep(2) after the .startxx method call works fine. But i have to send hundreds of records asynchronysly. If I write Thread.sleep(2), It will take 20 seconds for processing each request. I have to reduce this time as much as we can. Is there any other way to overcome this problem? Thanks, Aseem -- View this message in context: http://www.nabble.com/Asynchronous-web-services-using-Axis2-with-XMLBeans-binding-tp19373251p19373251.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Asynchronous web services using Axis2 with XMLBeans binding
On Mon, Sep 8, 2008 at 8:00 PM, Aseem Sharma [EMAIL PROTECTED]wrote: I am developing asynchronous web services using Axis2 with XMLBeans binding. 1)We are using this command to generate the client stubs WSDL2Java -uri ABC.wsdl -d xmlbeans -a 2)When calling stub's startxyz() method through our Client Program for asynchronous calling of our web service, the request is not going to server side and it is not showing any client side exception. 3)But when we change _operationClient.execute(true); line in startxyz() method of the client stub which was earlier _operationClient.execute(false); the request went to server side. Axis 1.4 version is used There is one solution to it. Putting Thread.sleep(2) after the .startxx method call works fine. But i have to send hundreds of records asynchronysly. If I write Thread.sleep(2), It will take 20 seconds for processing each request. I have to reduce this time as much as we can. Is there any other way to overcome this problem? This is something to manage with you application logic. There is no need to keep a sleep for every request. but you have to keep the client alive until it sends all the messages. thanks, Amila. Thanks, Aseem -- View this message in context: http://www.nabble.com/Asynchronous-web-services-using-Axis2-with-XMLBeans-binding-tp19373251p19373251.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Amila Suriarachchi, WSO2 Inc.
Re: [Axis2] Architecture: Asynchronous Web services with Axis1 and Axis2 -
william wallace wrote: Hi, So far, we have used Axis1 to create a number of Web services in my project. We see it works well with the request-response message pattern. Only one issue is that we could not have Asynchronous Web services. Instead, we have had to use Socket programming for those asynchronous in nature. (the client maintains a server Socket, after responding, the Web service has to initialize a client socket connecting to the client side program,...). The key shortcoming of this approach is that the socket connection must be maintained for a time even no data transfer in the case of event notification (the Web service informs back to the client side about an event happened). Now I just switch to Axis2 and find that it supports the Non-blocking invocation and I can use it for those Asynchronous Web services. The first thing I notice is, in Axis2, there is no difference in client (consumer) and Web service side. I would like to know how the Call Back mechanism has been implemented. - if HTTP is the transport, is there an http server in the client side opening to wait for the call-back message from Web service ? if not, what is really happening ? - if TCP is the transport, can I say that a server Socket is opened in the client side ? any long-running connection between the client and Web services ? Anyone has knowledge in this issue, please advise me. I do appreciate it. Thanks in advance __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com Hi William, I believe this podcast/article should tell you a bit about asynchronous web services invocations in Axis2. http://wso2.org/library/2774 Cheers! Suran - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] Architecture: Asynchronous Web services with Axis1 and Axis2 -
Hi, So far, we have used Axis1 to create a number of Web services in my project. We see it works well with the request-response message pattern. Only one issue is that we could not have Asynchronous Web services. Instead, we have had to use Socket programming for those asynchronous in nature. (the client maintains a server Socket, after responding, the Web service has to initialize a client socket connecting to the client side program,...). The key shortcoming of this approach is that the socket connection must be maintained for a time even no data transfer in the case of event notification (the Web service informs back to the client side about an event happened). Now I just switch to Axis2 and find that it supports the Non-blocking invocation and I can use it for those Asynchronous Web services. The first thing I notice is, in Axis2, there is no difference in client (consumer) and Web service side. I would like to know how the Call Back mechanism has been implemented. - if HTTP is the transport, is there an http server in the client side opening to wait for the call-back message from Web service ? if not, what is really happening ? - if TCP is the transport, can I say that a server Socket is opened in the client side ? any long-running connection between the client and Web services ? Anyone has knowledge in this issue, please advise me. I do appreciate it. Thanks in advance __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
