WS Addressing :: Issue with setting ReplyTo :: Axis2-1.1-SNAPSHOT

2006-10-10 Thread Vaibhav Pandey

Hi All,
I am trying to explore WS Addressing by creating a flow in which i call a WS
(INOUT-with NonBlockingDual client) and then i want the response to be
directed to another WS on a different port and server. I have explicitly set
the To/ReplyTo in my client. In the resluting SOAP request the wsa:To
parmeter gets set based on what i mentioned but somehow the wsa:ReplyTo is
set to the default listener address !!

I have also set::
options.setProperty(AddressingConstants.REPLACE_ADDRESSING_HEADERS,
Boolean.TRUE)
and then am setting replyto as ::   options.setTo(targetEPR);

options.setReplyTo(targetReplyEPR);

options.setTransportInProtocol(Constants.TRANSPORT_HTTP);

i also tried   ::
options.setProperty(AddressingConstants.WSA_REPLY_TO, targetReplyEPR);

but what i found after looking at the source code was that in the message
context itself the replyTo address is set to default whereas the To address
is set based on what i mentioned.

Kindly guide me as to what am i supposed to do.


Regards,
Vaibhav



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: WS Addressing :: Issue with setting ReplyTo :: Axis2-1.1-SNAPSHOT

2006-10-10 Thread Vaibhav Pandey
Hi,
Thanks for the prompt reply Eran, this issue was resolved yesterday after a
suggestion by Brian, that in such a scenario we should use fireandforget
instead of sendrecievenonblocking and this worked for meand that
comes out to be the same tht you have suggested :-)

thanks newayz.


Regards,
Vaibhav



-Original Message-
From: Eran Chinthaka [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 11, 2006 12:35 AM
To: axis-dev@ws.apache.org
Subject: Re: WS Addressing :: Issue with setting ReplyTo ::
Axis2-1.1-SNAPSHOT


I answered this question couple of time, but let me try again.

If you invoke send-receive from your client then your response *must*
come to it and Axis2 engine helps you to do that by starting up the
proper listeners.

What you could have done was invoke one way and put your replyTo. Even
if you are invoking an IN-OUT service, for your clients it is just
IN-Only as it won't receive a response.

But there was a valid scenario, actually pointed out by Chamikara, that
some might want to get his replies through a proxy like tcp-mon. Yes in
that case, you might want to override the replyTo value. I can remember
Chamikara was talking about this but not sure whether he implemented it.
Chamikara, you wanna add something here?

-- Chinthaka

Vaibhav Pandey wrote:
 Hi All,
 I am trying to explore WS Addressing by creating a flow in which i call a
WS
 (INOUT-with NonBlockingDual client) and then i want the response to be
 directed to another WS on a different port and server. I have explicitly
set
 the To/ReplyTo in my client. In the resluting SOAP request the wsa:To
 parmeter gets set based on what i mentioned but somehow the wsa:ReplyTo is
 set to the default listener address !!

 I have also set::
 options.setProperty(AddressingConstants.REPLACE_ADDRESSING_HEADERS,
 Boolean.TRUE)
 and then am setting replyto as :: options.setTo(targetEPR);
   
 options.setReplyTo(targetReplyEPR);
   
 options.setTransportInProtocol(Constants.TRANSPORT_HTTP);

 i also tried ::
 options.setProperty(AddressingConstants.WSA_REPLY_TO, targetReplyEPR);

 but what i found after looking at the source code was that in the message
 context itself the replyTo address is set to default whereas the To
address
 is set based on what i mentioned.

 Kindly guide me as to what am i supposed to do.


 Regards,
 Vaibhav



 -
 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]