Qpid
  1. Qpid
  2. QPID-3734

Qpid JCA AdminObjects should be refactored to use AMQDestination JavaBean

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.15
    • Component/s: JCA
    • Labels:
      None
    • Environment:

      All OS platforms, all supported JEE platforms.

      Description

      Currently we use the QpidDestinationProxy to managed our AdminObjects (QpidQueue, QpidTopic). Due to the way some application servers create and bind JCA AdminObjects into JNDI using a specialized javax.naming.NamingManager, this has caused some issues primarily due to the QpidDestinationProxy being created and bound directly into JNDI rather than the naming Reference.

      Rather than use the QpidDestinationProxy, the JCA AdminObject(s) should be refactored to use QpidQueue and QpidTopic as the primary AdminObjects for queues and topics. Note this effort will require the completion of QPID-3688.

      1. QPID-3734.patch
        52 kB
        Weston M. Price

        Issue Links

          Activity

          Hide
          Weston M. Price added a comment -

          Patch addresses issue.

          Show
          Weston M. Price added a comment - Patch addresses issue.
          Hide
          Weston M. Price added a comment -

          Adding patch to use new AMQDestination JavaBean conformance.

          Show
          Weston M. Price added a comment - Adding patch to use new AMQDestination JavaBean conformance.

            People

            • Assignee:
              Weston M. Price
              Reporter:
              Weston M. Price
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development