XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Won't Fix
    • None
    • None
    • JMS AMQP 0-x

    Description

      As the current C++ broker selector work stands it is compliant with the registered amqp 1.0 filter extension, but the JMS client will not use the C++ broker selectors for anything still falling back to the client side selectors.

      We should allow the JMS client to use the c++ broker selectors.

      There are roughly 2 ways to do this and both may be needed:

      For amqp 1.0 we need the client to translate the JMS specified identifiers to the ones specified in the extension and to use a filter - this may never be work sensible to do in the existing client.

      For earlier protocol versions, we probably need to add code to the C++ broker which accepts the extra subscription property that the java client uses for the selector and add some code which recognises the JMS identifiers instead of the amqp extension identifiers.

      Attachments

        1. Translator.java
          6 kB
          Gordon Sim

        Activity

          People

            Unassigned Unassigned
            astitcher Andrew Stitcher
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: