qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-7159) [Java Client] Disabling user ids in AMQP messages
Date Mon, 11 Apr 2016 17:45:25 GMT

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

ASF subversion and git services commented on QPID-7159:
-------------------------------------------------------

Commit 1738613 from orudyy@apache.org in branch 'java/branches/6.0.x'
[ https://svn.apache.org/r1738613 ]

QPID-7159: Add connection parameter to control whether a MessageProducer will populate the
JMSXUserID value for each sent message using the authenticated username from the connection

          Merged from trunk
          svn merge -c 1737853,1738610  ^/qpid/java/trunk

> [Java Client] Disabling user ids in AMQP messages
> -------------------------------------------------
>
>                 Key: QPID-7159
>                 URL: https://issues.apache.org/jira/browse/QPID-7159
>             Project: Qpid
>          Issue Type: New Feature
>          Components: Java Client
>            Reporter: Jakub Scholz
>            Assignee: Keith Wall
>             Fix For: qpid-java-6.0.2, qpid-java-6.1
>
>         Attachments: QPID-7159-Add-system-test.diff, QPID-7159-conn-option.patch, QPID-7159-rename-parameter-into-populateJMSXUserID.diff,
QPID-7159.patch
>
>
> The AMQP 0-10 JMS client seems to always attach the user-id message property to the AMQP
message. 
> In some cases, I don't think this is desired. For example when I send messages to my
customers, I do not really want them to know which other users exist on the broker and are
used to send messages.
> It would be great to have a possibility to disable the user-id when needed. 
> The attached patch disables the user id in the BasicMessageProducer based on a system
property qpid.attach_user_id (true/false). Does that look like a reasonable solution? If yes,
I can try to add some tests.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message