[
https://issues.apache.org/jira/browse/QPID-7159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216282#comment-15216282
]
Jakub Scholz commented on QPID-7159:
------------------------------------
Hi Alex,
You are right, connection option would be much better. I probably used system
property just because it was easier to implement at the moment - I do not have
any special reason why I need system property, so maybe we don't need it at
all.
I attached updated patch with new connection option attachUserId (I'm not sure
what is preferred - whether camel case or snake case - both seem to be used by
different options). Please have a look.
Thanks & Regards
Jakub
> [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
> Attachments: 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: [email protected]
For additional commands, e-mail: [email protected]
