[
https://issues.apache.org/jira/browse/WSCOMMONS-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen resolved WSCOMMONS-475.
---------------------------------------
Resolution: Fixed
Fix Version/s: Transports 1.0
I think it's actually the other way round: the individual transports should not
have to care about how messages are dispatched, since the logic is the same for
all transports (at least the type of transport implemented by
AbstractTransportListener; HTTP is of course different). Moved the duplicate
code to a common createMessageContext method.
> JMS Message Receiver Should Set the AxisMessage when Setting the AxisOperation
> ------------------------------------------------------------------------------
>
> Key: WSCOMMONS-475
> URL: https://issues.apache.org/jira/browse/WSCOMMONS-475
> Project: WS-Commons
> Issue Type: Bug
> Components: Transport
> Environment: Any
> Reporter: Hiranya Jayathilaka
> Assignee: Andreas Veithen
> Fix For: Transports 1.0
>
> Attachments: WSCOMMONS-475.patch
>
>
> JMSMessageReceiver in certain occasions set the AxisService and AxisOperation
> for incoming message contexts. But in such occasions it doesn't currently set
> the AxisMessage. With latest Axis2 this causes some problems when it comes to
> dispatching messages. This issue caused some JMS related samples to not
> function properly in Apache Synapse. Therefore as a simple fix we need to set
> the AxisMessage in JMSMessageReceiver along with the AxisOperation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
