[
https://issues.apache.org/jira/browse/QPID-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008799#comment-13008799
]
Weston M. Price commented on QPID-3131:
---------------------------------------
The original description of this bug was incorrect. In essence, the real issue
is that when using the ADDR syntax or when the exchange class cannot be
determined, the AMQDestination class will construct an AMQAnyDestination. By
default, all destinations use the AMQConnectionFactory as the
javax.naming.spi.ObjectFactory. However, the AMQConnectionFactory did not
provide for the creation of an AMQAnyDestination in getObjectInstance. The
attached patch (qpid-3131.patch) addresses this. A unit test has been added to
the ConnectionFactoryTest testing the new behavior.
> AMQConnectionFactory getObjectInstance does not recognize AMQDestination
> ------------------------------------------------------------------------
>
> Key: QPID-3131
> URL: https://issues.apache.org/jira/browse/QPID-3131
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.11
> Environment: All platforms. Java cilent.
> Reporter: Weston M. Price
> Fix For: 0.11
>
> Attachments: qpid-3131.patch
>
>
> Currently the AMQConnectionFactory does not allow for AMQDestination to be
> created in getObjectInstance. AMQDestination specifies AMQConnectionFactory
> as it's ObjectFactory, however, when an attempt is made to recreate the
> AMQDestination null is returned being that the AMQConnectionFactory does not
> provide for this type. This came up as a result of work on the JCA admin
> objects for destinations in the JCA adapter.
--
This message is automatically generated by JIRA.
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:[email protected]
