You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Ben Frank (JIRA)" <ji...@apache.org> on 2013/01/03 20:40:15 UTC

[jira] [Closed] (AMQ-4243) When converting an Exchange to an ActiveMQMessage the original JMS headers are lost.

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

Ben Frank closed AMQ-4243.
--------------------------

    Resolution: Not A Problem

Sorry! found a work around.

if you set {{?mapJmsMessage=false}} on the endpoint, and include {{?method=blah}} on the {{MessageListener}} then the type conversion isn't done and you get the original message that came from the queue.
                
> When converting an Exchange to an ActiveMQMessage the original JMS headers are lost.
> ------------------------------------------------------------------------------------
>
>                 Key: AMQ-4243
>                 URL: https://issues.apache.org/jira/browse/AMQ-4243
>             Project: ActiveMQ
>          Issue Type: Improvement
>            Reporter: Ben Frank
>
> Obviously the JMS headers aren't always available, but if they are it would be helpful to have them. 
> This is particularly apparent when using an existing {{MessageListener}} as an endpoint. If you're consuming from an ActiveMQ endpoint, the {{Message}} passed to {{MessageListener}} will not have the complete or valid JMS headers.
> Instead of creating a new {{ActiveMQMessage}} should either pass back the original as stored in the exchange, or an immutable copy.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira