Look at the (Save it and have look at it ... to see html formating)
http://svn.apache.org/repos/asf/webservices/axis2/branches/java/1_1/xdocs/userguide.html
See last part of the "Do a Non-Blocking Invocation" section
e.g.
Even though the above code does a non-blocking invocation at the
client API, still the transport connection may operate in blocking
fashion; for example a single HTTP connection can be used to make the
Web Service request and to get the response where a blocking
invocation happens at the transport level. To perform a "true"
Non-Blocking invocation in which two separate transport connections
are used for the request and response please add the following code
segment after creating the stub. These will force Axis2 to use
transport connections for the request and response while the client
uses a Callback to process the response.
stub._getServiceClient().engageModule(new QName("addressing"));
stub._getServiceClient().getOptions().setUseSeparateListener(true);
Once those options are set, Axis2 client does following
1. Start a new Transport Listener(Server) at the client side
2. Set the address of the Transport Listener, as the ReplyTo
WS-Addressing Header of the request Message
3. According to the WS-Addressing rules, Server will process the
request message and send the response back to the ReplyTo address
4. Client accepts the response, processes it and invokes the
callback with the response parameters
Hope this helps
Srinath
On 10/8/06, falom falom <[EMAIL PROTECTED]> wrote:
Hi,
Does axis2 support heavy async messaging be tween, let's say, two web
servers? Does that need help from i.e. JMS or MQ?
falom
________________________________
Mp3疯狂搜-新歌热歌高速下
--
============================
Srinath Perera:
Indiana University, Bloomington
http://www.cs.indiana.edu/~hperera/
http://www.bloglines.com/blog/hemapani
