You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commons-dev@ws.apache.org by "Andreas Veithen (JIRA)" <ji...@apache.org> on 2009/06/13 22:28:07 UTC

[jira] Assigned: (WSCOMMONS-475) JMS Message Receiver Should Set the AxisMessage when Setting the AxisOperation

     [ https://issues.apache.org/jira/browse/WSCOMMONS-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andreas Veithen reassigned WSCOMMONS-475:
-----------------------------------------

    Assignee: Andreas Veithen

> 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
>         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.