Bug 1070861 - Allow to expose all the amqp1.0 specific properties via 0-10 message application-properties
Summary: Allow to expose all the amqp1.0 specific properties via 0-10 message applicat...
Status: NEW
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp
Version: Development
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: messaging-bugs
QA Contact: Messaging QE
Depends On:
TreeView+ depends on / blocked
Reported: 2014-02-27 15:33 UTC by Petr Matousek
Modified: 2014-07-30 20:39 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Bugzilla 975444 None None None Never

Internal Links: 975444

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:

Note You need to log in before you can comment on or make changes to this bug.