[PROTON-711] [contrib/proton-jms] add support to message transformers for more efficient destination type annotation value

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: proton-0.8
• Assignee: Robbie Gemmell
• Reporter: Robbie Gemmell
• Created: 14/Oct/14 15:27
• Updated: 07/Jan/16 11:36
• Resolved: 14/Oct/14 15:36

Description

[contrib/proton-jms] add support to transformers for more efficient destination type annotation values

Historically the JMSDestination and JMSReplyTo values have had their Destination type information conveyed as strings that contain a comma seperated set of attributes from "queue", "topic", and "temporary". This isnt particularly efficient, either on the wire or when determining the value during inbound or outbound transformation on clients/brokers.

The OASIS JMS Mapping for AMQP is likely to use a byte to encode this information more efficiently. This change will add initial support (disabled by default to retain existing behaviour, brokers can enable it as and when they determine it appropriate) for using such a byte encoding within the proton-jms transformer code.

Issue Links

• is related to: PROTON-792 [contrib/proton-jms] remove stale support of byte destination type annotation from message transformers