[jira] [Resolved] (AMQ-2656) ActiveMQInitialConnectionFactory cannot return an XAConnectionFactory

["Gary Tully (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMQ-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully resolved AMQ-2656.
-----------------------------

       Resolution: Fixed
    Fix Version/s: 5.7.0


URL: http://svn.apache.org/viewvc?rev=1360125&view=rev
Log:
https://issues.apache.org/jira/browse/AMQ-2656 - add wellknown xa factory name, XAConnectionFactory so that context.lookup("XAConnectionFactory") will work as expected out of the box
                
> ActiveMQInitialConnectionFactory cannot return an XAConnectionFactory
> ---------------------------------------------------------------------
>
>                 Key: AMQ-2656
>                 URL: https://issues.apache.org/jira/browse/AMQ-2656
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JMS client
>    Affects Versions: 5.3.0
>            Reporter: Edan idzerda
>            Assignee: Gary Tully
>             Fix For: 5.7.0, 5.4.0
>
>         Attachments: ActiveMQInitialContextFactory.java, ActiveMQInitialContextFactory.java
>
>
> ActiveMQInitialContextFactory cannot resolve the name "XAConnectionFactory"  a la:
> INFO: JNDI API lookup failed: javax.naming.NameNotFoundException: XAConnectionFactory
> This prevents using the builtin JNDI service in an XA transaction context.  I've created a simple patch to workaround this and discussed it on the mailing list:  http://old.nabble.com/ActiveMQ%27s-JNDI-does-not-resolve-XAConnectionFactory-td27936255.html

--
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