[
https://issues.apache.org/jira/browse/AXIS2-2892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas resolved AXIS2-2892.
-------------------------------------
Resolution: Fixed
> Axis2 replyTo EPR is not stable
> -------------------------------
>
> Key: AXIS2-2892
> URL: https://issues.apache.org/jira/browse/AXIS2-2892
> Project: Axis 2.0 (Axis2)
> Issue Type: Improvement
> Components: kernel
> Reporter: Matt Lovett
> Priority: Minor
> Attachments: reply.patch
>
>
> This is an issue that cropped up while doing some interop testing with
> Sandesha, and .net. We were invoking serveral operations on a service, and
> were async-on-the-wire. The algorithm that the engine uses to choose the
> replyTo address includes the operation name, which means that the replyTo
> address changes from message to message.
> The .net runtime doesn't like it when the replyTo changes... so the testcase
> failed. There doesn't seem to be any need to include the operation name in
> the replyTo, so it seemed simplest to ignore it, and build the replyTo based
> on the service name.
> I'll attach a patch shortly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
