Uploaded image for project: 'ActiveMQ Classic'
  1. ActiveMQ Classic
  2. AMQ-5591

AMQP Implement the JMS Mapping spec as it evolves.

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 5.11.0, 5.11.1
    • 5.13.0
    • AMQP
    • None

    Description

      The AMQP JMS Mapping specification is currently under development at OASIS. This issue covers work to be done to implement the mechanics necessary on the broker side to allow for JMS clients that operate over AMQP.

      Attachments

        1.
        AMQP: Pull in Proton JMS transformer code and refactor to enable both JMS mapping and support for AMQP clients Sub-task Resolved Timothy A. Bish
        2.
        AMQP: Implement support for Temporary Topics Sub-task Resolved Timothy A. Bish
        3.
        AMQP: clean up durable subscription unsubscribe handling to simplify and resolve issues Sub-task Resolved Timothy A. Bish
        4.
        AMQP: Create simple Proton based client to be used in testing Sub-task Resolved Timothy A. Bish
        5.
        AMQP: Clean up unit test start / stop code, excessive thread creation casuse slowdowns. Sub-task Resolved Timothy A. Bish
        6.
        AMQP: Update the AMQP 1.0 JMS client with newest QPid-JMS Release Sub-task Resolved Timothy A. Bish
        7.
        AMQP - delayed authentication from SASL connect leads to race on client end. Sub-task Resolved Timothy A. Bish
        8.
        AMQP: Connection open pump to socket twice in the error case when only once is needed. Sub-task Resolved Timothy A. Bish
        9.
        AMQP: Remove direct usage of types from the legacy QPid JMS 1.0 client from the tests Sub-task Resolved Timothy A. Bish
        10.
        AMQP: dont list filters which are not actually being applied in AMQP attach responses Sub-task Resolved Unassigned
        11.
        AMQP: use type descriptors to inspect AMQP filter types rather than the map keys Sub-task Resolved Timothy A. Bish
        12.
        AMQP: Add support for delete of temporary destinations Sub-task Resolved Timothy A. Bish
        13.
        AMQP: add support for mapping JMSType header to AMQP message Subject Sub-task Resolved Unassigned
        14.
        AMQP: Update JMS Outbound transformer to add the mapping compliant destination type markers Sub-task Resolved Timothy A. Bish
        15.
        AMQP: Add connection property to open frame when connection attempt has failed Sub-task Resolved Timothy A. Bish
        16.
        AMQP: Honor receiver flow as the true prefetch value on a link. Sub-task Resolved Timothy A. Bish
        17.
        AMQP: Create unit tests to validate behavior of AMQP implementation against spec and mapping requirements. Sub-task Resolved Timothy A. Bish
        18.
        AMQP: add a hint to the error condition to signal that container-id was the invalid field when clientid is in use Sub-task Resolved Robbie Gemmell

        Activity

          People

            tabish Timothy A. Bish
            tabish Timothy A. Bish
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: