[
https://issues.apache.org/activemq/browse/AMQ-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58311#action_58311
]
Edan idzerda edited comment on AMQ-2656 at 3/18/10 8:25 PM:
------------------------------------------------------------
Gary, will your patch (I can't see it yet) allow me to JNDI lookup
"XAConnectionFactory" ? That may be all I have available in webMethods "JNDI
Provider Alias" settings. I guess I can try to lookup connection.MyConnection
or something along those lines.
was (Author: edan):
Gary, will your patch (I can't see it yet) allow me to JNDI lookup
"XAConnectionFactory" ? That may be all I have available in webMethods "JNDI
Provider Alias" settings.
> ActiveMQInitialConnectionFactory cannot return an XAConnectionFactory
> ---------------------------------------------------------------------
>
> Key: AMQ-2656
> URL: https://issues.apache.org/activemq/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.4.0
>
> Attachments: 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.
-
You can reply to this email to add a comment to the issue online.
