Thank you Srinath!
In both your scenarious, the presence of firewalls and NAT brings about
a complex problem since it is problematic for a service to contact a
client listener.
In this situation, the reasonable way can be to organize a polling
client, which periodically asks a service, whether the service has
finished its job.
But in this case, the service implementation is not trivial.
Thanks
German
Srinath Perera schrieb:
Axis2 client API give you two choices
1) InOutMEPClient, here if you specify "use Seperate Listener" in
setTransportInfo(..) Axis2 will start a Listener for you and set the
Reply-To WS-A Headers to the listener. (The service provider initiate
a second connection.) Here if you are behind a fire wall and private
IP address things get complex.
2) MessageSender .. here you can set the all the addressing Headers
and control the interaction. But you should start your own Listener
and set ReplyTo correctly. You may have a Proxy that foward the
Message to correct recipient or use polling. But it up to you to
implement this as Message Sender do handle only one interaction.
Thanks
Srinath
On 11/15/05, German Sakaryan <[EMAIL PROTECTED]> wrote:
Hello all,
Can anybody explain non-blocking dual transport invocation with axis 2?
Please.
Axis2 provides a possibility to make a non blocking calls and in the
same time to use "Transport Level Asynchrony"
In this way, axis uses "separate transport connections for request and
response".
My question is: who (service or client) does
initiate the second connection for response?
Does it mean that client should be available (public IP etc.)?
In other way, can my client run behinf firewall and NAT?
Thank you,
German Sakaryan
--
Dr.-Ing. German Sakaryan
Computer Science Dept.
University of Rostock
Tel: +49 381 498-7585
Fax: +49 381 498-7642
E-mail: [EMAIL PROTECTED]
Home: http://www.informatik.uni-rostock.de/~gs137
