A question about the JNDI context. When someone checks an
XAConnection out of the pool, it needs to register with the
TransactionManager. It gets a handle to the TransactionManager via a
JNDI lookup. I've seen on the list that you can create an InitialContext
from which to do a lookup simply with new InitialContext() if your
configuration files are placed appropriately.
First, does this also work on the server side? I think everyone's
been asking about client use so far.
And second, will this work correctly? It looks like the current
Transaction is stored in a ThreadLocal, so any time you get the
TransactionManager from JNDI it will return the same one, but when it goes
to look up the Transaction it will find the correct ThreadLocal one. Just
want to make sure I'm not missing some subtlety that would cause me to
have to load a specific context somehow to get the correct transaction.
Aaron
