Hi, there were also content-type requirements without solution due to specification gaps.
I think there should be a way for a consumer of this library to extend the mapping between AMQP headers / annotations / properties and JMS properties. Allowing users to introduce and support vendor-specific properties would solve other and probably future requests as well. Best regards Jens -- Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
