David Jencks wrote:
Your proposal will break almost any usage of local tx jdbc. If you really
feel this is the best solution please write a separate ConnectionManager
not used by the LocalTx stuff.
This is what I meant by "better implementation".
I think your solution is also woefully ineffici
David Jencks wrote:
I've looked at this in more detail and am 99.9% sure this proposal is a bad
idea. I think it will break local tx support.
I also think using the 4.0 xa wrapper will solve the problem.
I agree that suggested implementation breaks local tx and in this sense
is "bad". However
Ok, here is the same example with some more details/comments. There was
a mistake in my original explanation and I apoligize for confusion.
BeanA allocates a connection
- TxConnectionManager.getManagedConnection allocates
new managed connection mc1 of type
org.jboss.resource.adapter.jdb