[
https://issues.apache.org/jira/browse/AMQ-4426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13771972#comment-13771972
]
Gary Tully commented on AMQ-4426:
---------------------------------
https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=c3875222 is
also relevant to ensure we don't default to a local tx or autoack after an abort
> Allow XAPooledConnectionFactory to be used from ee ( implement ObjectFactory,
> [Queue|Topic]ConnectionFactory
> ------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-4426
> URL: https://issues.apache.org/jira/browse/AMQ-4426
> Project: ActiveMQ
> Issue Type: New Feature
> Components: activemq-pool
> Affects Versions: 5.8.0
> Environment: ee container eg: jboss
> Reporter: Gary Tully
> Assignee: Gary Tully
> Labels: connectionfactory, ee, jboss, jta, pool, xa
> Fix For: 5.9.0
>
>
> To easily bind a connection factory that is aware of the containers
> transaction manager(tm) the use of javax.naming ObjectFactory comes in handy.
> This allows the connection factory to create instances from a jndi lookup.
> Having the tm resolved from jndi at runtime makes sense to avoid wiring
> dependencies.
> Having the XAPooledConnectionFactory implement the ee type Queue and Topic
> connection factory interfaces makes such a factory useable.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
