[
https://issues.apache.org/jira/browse/WSCOMMONS-475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12717902#action_12717902
]
Hiranya Jayathilaka commented on WSCOMMONS-475:
-----------------------------------------------
We could do this in base transport listener's handleIncomingRequest method but
my personal opinion is that this should be handled by the individual
transports. They are the ones who set the AxisService and the AxisOperation to
the message context, so IMO it's really their responsibility to set the
AxisMessage along with them. I've done this change for the FIX transport a few
days back since some of the samples were not working properly.
> 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.
