You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Weston M. Price (Assigned) (JIRA)" <ji...@apache.org> on 2012/01/09 22:35:42 UTC
[jira] [Assigned] (QPID-3734) Qpid JCA AdminObjects should be
refactored to use AMQDestination JavaBean
[ https://issues.apache.org/jira/browse/QPID-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Weston M. Price reassigned QPID-3734:
-------------------------------------
Assignee: Weston M. Price
> Qpid JCA AdminObjects should be refactored to use AMQDestination JavaBean
> -------------------------------------------------------------------------
>
> Key: QPID-3734
> URL: https://issues.apache.org/jira/browse/QPID-3734
> Project: Qpid
> Issue Type: Improvement
> Components: JCA
> Environment: All OS platforms, all supported JEE platforms.
> Reporter: Weston M. Price
> Assignee: Weston M. Price
> Priority: Minor
> Fix For: 0.15
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org