Ok, thanks.
Sent from my iPhone
On Nov 24, 2009, at 1:01 PM, Jonathan Halliday <jonathan.halliday(a)redhat.com
The 3rd party pools out there will only pool Connection, not
XAConnection, so they are largely useless to JBossTS.
The current architecture I have for the JBossTS+tomcat prototype
puts the transaction manager directly on top of the driver's own
XADataSource. Most db vendor implementations of that have built-in
pooling, so JBossTS TransactionalDriver does not pool itself, nor
use a 3rd party pool.
The code does weird tomcat specific classloader hacks, but you
should be able to 'borrow' 90% of what you need from it if you want
to go with a JCA-free design:
http://anonsvn.jboss.org/repos/labs/labs/jbosstm/workspace/jhalliday/tomc...
Jonathan.
On 11/23/2009 05:34 PM, Gavin King wrote:
> Yes, I understand the need for XA enlistment, but JBoss Transactions
> is already able to do that, right? What I'm saying is that you would
> use the TransactionalDriver together with a pool. Or does
> TransactionalDriver already do pooling?
...
--
------------------------------------------------------------
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
Street, Windsor, Berkshire, SI4 1TE, United Kingdom.
Registered in UK and Wales under Company Registration No. 3798903
Directors: Michael Cunningham (USA), Charlie Peters (USA), Matt
Parsons (USA) and Brendan Lane (Ireland)