You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "clebert suconic (JIRA)" <ji...@apache.org> on 2018/09/04 17:25:00 UTC

[jira] [Closed] (ARTEMIS-2058) Allow setting of any value (not just bytes) in AMQPMessage.extraProperties

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

clebert suconic closed ARTEMIS-2058.
------------------------------------
    Resolution: Fixed

> Allow setting of any value (not just bytes) in AMQPMessage.extraProperties
> --------------------------------------------------------------------------
>
>                 Key: ARTEMIS-2058
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2058
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>          Components: AMQP
>            Reporter: Carsten Lohmann
>            Priority: Major
>             Fix For: 2.7.0
>
>
> When developing an incoming or outgoing AMQP interceptor, there may be scenarios where extra properties should be put on the AMQP message, without changing the original message (e.g. for ARTEMIS-2028).
> For this, the {{AMQPMessage.extraProperties}} look suitable. These properties are restricted to contain only byte[] values though - otherwise there will be an exception in {{AmqpCoreConverter.toCore()}}.
> It would be good to support any kind of values here.
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)