| |
Previous versions of jboss provided database connectivity and connection pooling through the XADataSourceLoaderMBean. This was normally used with the XADataSourceImpl, which provided an xa interface for a non-xa jdbc driver. Of course, since the underlying driver did not support xa transactions, neither did the XA wrapper. These drivers can now be used with the Minerva JDBC LocalTransaction ResourceAdapter, which works with the transaction manager using local, non-xa transactions, eliminating the confusion of imitating but not implementing xa semantics. If you have a true XADataSource implementation for your database, you can instead use the Minerva JDBC XATransaction ResourceAdapter, which provides full xa support.
Most of the parameters in an XADataSourceLoader configuration have direct parallels in a ConnectionFactoryLoader configuration.
Normally the easiest migration path is to select a configuration example for your database from the provided examples and to modify it until it works. If you find errors or work out a configuration for a database for which there is no example, please contribute back to the JBoss community by supplying us with your configuration. Questions on this subject should be asked in the Database and Persistence forum.
Migration results in the following conversions:
An XADataSourceLoader using the XADataSourceImpl wrapper converts to the LocalTransaction resource adapter and the LocalTransaction pool.
An XADataSourceLoader using some other XADataSource class converts to the XATransaction resource adapter and the XATransaction pool.
A JDBCDataSourceLoader converts to the LocatlTransaction resource adapter and the NoTransaction pool. Note that clients using connections from this connection factory are completely in charge of transactions, and must use the connection.commit/rollback methods since UserTransaction works through the Transaction Manager which has no communication with the connection.
 | |