[
https://issues.apache.org/jira/browse/ARTEMIS-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16201768#comment-16201768
]
ASF GitHub Bot commented on ARTEMIS-1461:
-----------------------------------------
Github user Matze2 commented on the issue:
https://github.com/apache/activemq-artemis/pull/1584
I tried the latest snapshot with an AmqpInterceptor implementation. This
does not work.
```
@Override
public boolean intercept(final AMQPMessage message, RemotingConnection
connection) {
logger.info("AMQP Interceptor gets called with message " +
message.getMessageID());
logger.info("Properties before: " + message.getPropertyNames());
message.putStringProperty("newProp", "newPropValue");
logger.info("Properties after: " + message.getPropertyNames());
return true;
}
```
The listener does not see the "newProp" property added here.
Will try the broker plugin example now.
> Allow Property changes on AMQP message and reencode
> ---------------------------------------------------
>
> Key: ARTEMIS-1461
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1461
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.3.0
> Reporter: clebert suconic
> Assignee: clebert suconic
> Fix For: 2.4.0
>
>
> AMQP messages are immutable by default, but it should be possible, if the
> user decided to do so, to change messages and re encode them
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
