activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-6353) AMQP: Using JMS Transformer, preserve the type of the original CorrelationId
Date Tue, 12 Jul 2016 18:17:20 GMT

    [ https://issues.apache.org/jira/browse/AMQ-6353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15373373#comment-15373373
] 

Timothy Bish commented on AMQ-6353:
-----------------------------------

Similar situation to the MessageId encoding. 

> AMQP: Using JMS Transformer, preserve the type of the original CorrelationId
> ----------------------------------------------------------------------------
>
>                 Key: AMQ-6353
>                 URL: https://issues.apache.org/jira/browse/AMQ-6353
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: AMQP
>    Affects Versions: 5.13.3
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>             Fix For: 5.14.0, 5.13.4
>
>
> When transforming the incoming message using the JMS Transformer the type of the incoming
correlation ID is lost when stored in the string value in the Message object, we need to preserve
that type as this is meant to be immutable.  Because the ActiveMQMessage object's only have
a text value for correlation ID we need to encode the incoming value to a string form and
apply prefix values to allow for re-encoding the correlation to the original type on the way
out.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message