[QPID-3734] Qpid JCA AdminObjects should be refactored to use AMQDestination JavaBean

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 0.15
• Component/s: JCA

Environment

All OS platforms, all supported JEE platforms.

• Assignee: Weston M. Price
• Reporter: Weston M. Price
• Created: 07/Jan/12 00:58
• Updated: 06/Sep/16 20:27
• Resolved: 03/Feb/12 07:20

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.

Issue Links

• depends upon: QPID-3688 AMQDestination and children should conform to the JavaBean pattern
• is depended upon by: QPID-3701 Add support for Glassfish Application Server to Qpid JCA Adapter