[QPID-7434] Mature the AMQP message conversion layer (headers and content)

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: qpid-java-broker-7.0.0
• Component/s: Broker-J
• Assignee: Lorenz Quack
• Reporter: Keith Wall
• Created: 23/Sep/16 09:56
• Updated: 14/Nov/17 21:59
• Resolved: 11/Aug/17 14:15

Description

There are a number of gaps in our message converters that mean some message are not converted with complete fidelity (particularly in the treatment of application headers), and where complete fidelity cannot be acheived we need sensible rules, uniformly implemented to decide how aspects degrade.

For instance, for AMQP 0-8..0-10 allow application headers whose values were complex types (e.g. map). AMQP 1.0 disallows this. What should the behaviour be? Should the header be dropped?

Another instance is the length and constituency of the keys of application headers. AMQP 0-8..0-10 have a protocol restriction of 255 UTF8 bytes. AMQP has supports longer strings. Also AMQP 0-9 says further restricts the key to be formed like a Java identifier.

Issue Links

• is related to: QPID-7366 [Java Broker] Add Management operation to VirtualHost to allow publishing of messages through management
• relates to: QPID-7602 Message reply-to conversion between protocols for point to point and publish subscribe messaging patterns