You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2015/02/17 21:26:11 UTC

[jira] [Created] (AMQ-5592) AMQP: Pull in Proton JMS transformer code and refactor to enable both JMS mapping and support for AMQP clients

Timothy Bish created AMQ-5592:
---------------------------------

             Summary: AMQP: Pull in Proton JMS transformer code and refactor to enable both JMS mapping and support for AMQP clients
                 Key: AMQ-5592
                 URL: https://issues.apache.org/jira/browse/AMQ-5592
             Project: ActiveMQ
          Issue Type: Sub-task
          Components: AMQP
    Affects Versions: 5.11.0
            Reporter: Timothy Bish
            Assignee: Timothy Bish
             Fix For: 5.12.0


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.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)