Skip to content

Conversation

@Havret
Copy link

@Havret Havret commented Sep 18, 2024

Hi @gemmellr, @michaelandrepearce, @tabish121 could you please take a look? This PR adds access to content-encoding property of the underlying AMQP message. The implementation is based on Advanced Message Queuing Protocol (AMQP) JMS Mapping Version 1.0 Working Draft 9.

@Havret Havret force-pushed the QPIDJMS-295_Add-support-for-content-encoding-property branch from c266c95 to 228f05a Compare September 18, 2024 20:31
@michaelandrepearce
Copy link
Contributor

Lgtm.

@gemmellr

@zertan
Copy link

zertan commented Oct 30, 2025

Hi guys. This is and the possibility to read/set content-type also is becoming quite urgent. Any new developments?

@zertan
Copy link

zertan commented Oct 30, 2025

@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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants