You can either use reflection magic as you put it, or you can take a
squint at using the JMSMessage.getFacade() method and the
TraceableMessage#getTracingAnnotation method its return value
implements.
On Mon, 6 Sept 2021 at 15:26, Thomas Kettenbach <tkett...@gmail.com> wrote:
>
> Hi,
>
> a colleague is using Apache QPID JMS to consume our data services hosted on
> a RabbitMQ using AMQP1.0 protocol. We're publishing the messages using qpid
> proton c++ binding, and thus are flexible and utilizing the AMQP1.0
> features.
>
> In some of our AMQP1.0 messages we are including arbitrary properties to
> the "message-annotations", e.g. Content-MD5 for message verification.
>
> On a qpid-proton consumer implemented in python, we're easily accessing the
> message-annotation for example:
>
> AnnotationDict({symbol('Content-MD5'): '<some hex number>'})
>
> Using Qpid JMS, it is not easily accessible. My colleague mentioned some
> "Java Reflection magic".
>
> How are your thoughts on adding arbitrary properties, e.g. Message
> Verification checksums, etc. to AMQP messages in a hybrid environment? Are
> there any best practices or usage guidelines?
>
> BR,
> Thomas
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
