We have developed a pooling scheme that is a kind of hybrid between the
SharedLocalTransactionCM and the
XAConnectionManager ...
Without tx context (read usage), the pool dispenses for each separate
allocation request a different XA-enabled connection.
Within a single tx context (read&write usage), the pool dispenses a single
connection per factory for optimisation and cross-bean-instance
coherence purposes (e.g., imagine a OR-mapping resource with a transactional
in-memory cache per connection).
Would anyone be interested in me polluting the org.jboss.pool.connector
package with this?
CGJ
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
