I have documented how the new pooling and XA support works.

I think the new support is much more straightforward to use and gives better error reporting.

For example in the old pooling support if you use the pooling and xa enabled DSF "H2-pool-xa" and forget to install a TransactionManager or the pooling module the DataSource is simply not created. There is no error in the log as the config module can not know if the enhanced DSF is just not yet there or will never come up.

In the new pooling and XA support there will be a good error in the log if either the pooling or the TransactionManager are missing.

See

https://ops4j1.jira.com/wiki/display/PAXJDBC/Pooling+and+XA+support+in+1.0.0

Christian

--
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
http://www.talend.com

--
--
------------------
OPS4J - http://www.ops4j.org - ops4j@googlegroups.com

--- You received this message because you are subscribed to the Google Groups "OPS4J" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ops4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to