Major Description
We currently use the Proton-JMS library to help with conversions of AMQP messages and creating destinations from links and message To fields. This works to a point but becomes inflexible when trying to deal with the variety of clients that are interacting with the broker and the upcoming JMS mapping spec adds complexity to this. We need to be more agile with fixes and support the old JMS client were possible. Waiting on Proton releases and trying to create a one size fits all options for the mapping has proven ineffective.
We should use the current JMS transformation code as a base to better implement AMQP support in the broker and allow for faster fixes to issues as they arise.