AddressingOutHandler.processReplyTo may add an invalid ReplyTo on an outbound
client invoke in certain circumstances
--------------------------------------------------------------------------------------------------------------------
Key: AXIS2-1046
URL: http://issues.apache.org/jira/browse/AXIS2-1046
Project: Apache Axis 2.0 (Axis2)
Issue Type: Bug
Components: Addressing
Reporter: David Illsley
Assigned To: David Illsley
As outlined in [1] I have a problem with an invalid ReplyTo being set even if
isUseSeparateListener is not set.
I *think" this is caused by the support for SOAP Session Scope which I found
details of at [2]
I don't believe that this belongs in the AddressingOutHandler but in the
interests of a quick resolution (which I need) I have found a solution which is
to only set the ReplyTo EPR to the ServiceContext EPR if
msgContext.isServerSide() == true. This fixes the problem that I was seeing,
allows all the Axis2 tests to pass unaltered and should have no effect on the
SOAP Session Scope code.
[1] http://marc.theaimsgroup.com/?l=axis-dev&m=115557042925408&w=2
[2] http://www.developer.com/services/article.php/10928_3620661_1
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
