[
https://issues.apache.org/jira/browse/WSCOMMONS-475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12717655#action_12717655
]
Andreas Veithen commented on WSCOMMONS-475:
-------------------------------------------
I think we should go a step further and move the corresponding code (which
seems to be copy & paste) in the FIX, VFS, JMS and mail (to be confirmed)
transports to a common method in axis2-transport-base and fix it once and for
all.
> 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
> 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.
