Angel, I'd suggest you to read these 2 threads http://www.nabble.com/asynchronous-messaging-question-tf3219718.html#a8941644 http://www.nabble.com/Axis2-question-about-async.-invocation-of-web-services-tf3364140.html#a9359642
Michele On Mon, 2007-04-02 at 17:49 +0300, Angel Todorov wrote: > Hi Michelle, > > Thanks. Then what is the purpose of asynchronous message receivers ? > > Regards, > Angel > > On 4/2/07, Michele Mazzucco <[EMAIL PROTECTED]> wrote: > > Angel, > > > > as far as I know on the server side requests are processed in a > > synchronous way (I think only the sun implementation allows for > > asynchronous processing on the server side [1]). > > If the client is asynchronous a 200 (ok) code is sent back to the > > client, then the server processes the request. When the response is > > ready it will be sent using ws-addressing information. > > > > Michele > > > > [1] https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html > > > > On Mon, 2007-04-02 at 17:38 +0300, Angel Todorov wrote: > > > On the other hand, on the > > > server-side there is the concept of asynchronous message receivers > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
