Re: ActiveMQ's JNDI does not resolve XAConnectionFactory

2010-03-18 Thread Gary Tully
Yea, it is a simple in memory hash map configured from the environment. I was thinking of a new property, xa=true|false that could trigger the creation of an XA variant of the connection factory. I think doing XA by default may upset clients what check for an XA connection factory, transaction wrap

Re: ActiveMQ's JNDI does not resolve XAConnectionFactory

2010-03-18 Thread edan
Gary Tully wrote: > > you need to change > the > org.apache.activemq.jndi.ActiveMQInitialContextFactory.createConnectionFactory(Hashtable) > method to optionally create an ActiveMQXAConnectionFactory > I think it would be a sensible default but having a property that can > ensure > that a partic

Re: ActiveMQ's JNDI does not resolve XAConnectionFactory

2010-03-18 Thread Gary Tully
you need to change the org.apache.activemq.jndi.ActiveMQInitialContextFactory.createConnectionFactory(Hashtable) method to optionally create an ActiveMQXAConnectionFactory I think it would be a sensible default but having a property that can ensure that a particular factory is xa would be a nice a