[
https://issues.apache.org/jira/browse/ARTEMIS-2168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16680457#comment-16680457
]
Michael Andre Pearce edited comment on ARTEMIS-2168 at 11/8/18 9:57 PM:
------------------------------------------------------------------------
This was reported internally in my org.
I _+assume+_ (please take this just as a working assumption i haven't spent
time to fully work out how historically) it was previously working before
native AMQP message support. As all protocol messages used to be converted to
CORE, then the logic to set user existed (if the flag was true) operating on
CORE message, and then would be converted back to which ever protocol.
When AMQPMessage was added, this initial conversion was avoided, but ability to
set/change the user (JMSXUserID in JMS parlance) was not introduced.
was (Author: michael.andre.pearce):
This was reported internally in my org.
I assume it was previously working before native AMQP message support. As all
protocol messages used to be converted to CORE, then the logic to set user
existed (if the flag was true) operating on CORE message, and then would be
converted back to which ever protocol.
When AMQPMessage was added, this initial conversion was avoided, but ability to
set/change the user (JMSXUserID in JMS parlance) was not introduced.
> Fix "populate-validated-user" feature for AMQP produced messages
> ----------------------------------------------------------------
>
> Key: ARTEMIS-2168
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2168
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Michael Andre Pearce
> Priority: Major
>
> Fix feature: https://issues.apache.org/jira/browse/ARTEMIS-584 for AMQP
> produced messages.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
