commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Gregory <garydgreg...@gmail.com>
Subject [dbcp] XA support vs. normal DataSources
Date Sat, 13 Feb 2016 18:16:27 GMT
Hi All:

I was able to get pooling for a JDBC driver simply by doing:

DriverAdapterCPDS driverAdapterCPDS = new DriverAdapterCPDS();
driverAdapterCPDS.setUrl("jdbc:my:url:...");

Our CustomDataSource implements DataSource, Referenceable, AutoCloseable
but not javax.sql.ConnectionPoolDataSource.

So first, is that be best way to get pooling for a DataSource that does not
implement javax.sql.ConnectionPoolDataSource?

Next up, we have a XACustomDataSource that extends CustomDataSource in
order to create our own XAConnection.

Since interface XAConnection extends PooledConnection, an implementation is
left to provide some pooling.

Can DBCP help here or is there plans to support XA in someway in a future
version?

Aside from my XAConnection copying the kind of code
in org.apache.commons.dbcp2.managed.TesterBasicXAConnection?

Thank you all,
Gary

-- 
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message