[
https://issues.apache.org/jira/browse/QPIDJMS-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18034202#comment-18034202
]
ASF GitHub Bot commented on QPIDJMS-295:
----------------------------------------
zertan commented on PR #52:
URL: https://github.com/apache/qpid-jms/pull/52#issuecomment-3468590855
@gemmellr I think we need to relax some of the strictness with regards to
JMS for this. Is the priority to adhere to JMS standards or AMQP standards? I
think a good approach would be to think about downstream projects (for instance
camel-amqp).
> AMQP property content-encoding cannot be retrieved via
> JMS_AMQP_ContentEncoding
> -------------------------------------------------------------------------------
>
> Key: QPIDJMS-295
> URL: https://issues.apache.org/jira/browse/QPIDJMS-295
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
> Affects Versions: 0.23.0
> Reporter: Leo Riguspi
> Priority: Major
>
> The AMQP property content-encoding can be set but not retrieved:
> 1. Create a message and set the vendor property JMS_AMQP_ContentEncoding=gzip
> using QPid JMS
> 2. Send the message to an ActiveMQ broker via AMQP 1.0 with
> transport.transformer=jms (native does not work!)
> 3. Retrieve the message with QPid JMS: the property JMS_AMQP_ContentEncoding
> does not exist anymore in the message and there seem to be no other way of
> retrieving the content-encoding.
> Note that when consuming the same message with a python client the property
> seems to be set and accessible via the message.content_encoding field.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
