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
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Resolution||Fixed [ 1 ]|
|Assignee||Weston M. Price [ wprice ]|