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):
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
The specially named amqp1.0 specific properties are silently not transmitted to the amqp0-10 receiver
Thread the specially named amqp1.0 specific properties as common 0-10 application properties