[
https://issues.apache.org/jira/browse/QPIDJMS-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15218962#comment-15218962
]
ASF subversion and git services commented on QPIDJMS-163:
---------------------------------------------------------
Commit 20b458567a7b466bda22c5be7b26f367c8a3e778 in qpid-jms's branch
refs/heads/master from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=20b4585 ]
QPIDJMS-163 Add support for setting the authenticated User ID value from
the connection into messages that are sent. Default is to not populate
the user id portion of the message and can be enabled via the
configuration option jms.populateJMSXUserID=true
> support populating the user-id field on produced messages
> ---------------------------------------------------------
>
> Key: QPIDJMS-163
> URL: https://issues.apache.org/jira/browse/QPIDJMS-163
> Project: Qpid JMS
> Issue Type: Improvement
> Components: qpid-jms-client
> Reporter: Robbie Gemmell
> Assignee: Timothy Bish
>
> Whilst the client supports using the JMS-defined "JMSXUserID" property to
> interact with the contents of the binary user-id field on incoming AMQP
> messages, it does not yet support automatically populating the value on
> messages being sent by producers. We should add this support along with a
> config toggle to enable/disable it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
