Bug 1070861

Summary: Allow to expose all the amqp1.0 specific properties via 0-10 message application-properties
Product: Red Hat Enterprise MRG Reporter: Petr Matousek <pematous>
Component: qpid-cppAssignee: messaging-bugs <messaging-bugs>
Status: NEW --- QA Contact: Messaging QE <messaging-qe-bugs>
Severity: low Docs Contact:
Priority: low    
Version: DevelopmentCC: gsim, jross
Target Milestone: ---Keywords: Improvement
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Petr Matousek 2014-02-27 15:33:21 UTC
Description of problem:

Currently the new amqp1.0 standard properties (specially named, x-amqp-*, see Bug 975444) behaves like reserved names for amqp1.0. amqp0-10 receiver can not read them even if send (regardless what protocol is used by the sender amqp0-10/amqp1.0).

I believe that it would be less confusing if we allow to pass them as common
application-properties to the amqp0-10 message, even if they are not defined in the amqp0-10 standard.

The 1.0 -> 0-10 conversion probably wouldn't hurt to expose all the 1.0 specific properties via application-properties with the special names. 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. send a message with amqp1.0 specific property (x-amqp-*) over amqp1.0/amqp0-10
2. receive the message using amqp0-10 consumer
2. the application properties section of received message contains the x-amqp-* property

Actual results:
The specially named amqp1.0 specific properties are silently not transmitted to the amqp0-10 receiver

Expected results:
Thread the specially named amqp1.0 specific properties as common 0-10 application properties

Additional info: