On 2002.01.16 16:15:12 -0500 Kris Kristensen wrote: > Could somebody please shed some light on the difference between these, > and explain which one shold be used for XA > > ---JDBCDataSourceLoader
No transaction control possible from jboss. Use only from e.g. servlets where you are calling commit on your connections yourself. > ---RawXADataSourceLoader Something added at some point to help with the xa jca wrapper I believe. I don't know of any valid use, since you can specify the XADataSource class directly now. > ---XADataSourceLoader.java MBean that you should use for setting up a usable DataSource that your ejb's and JAWS can use in jboss 2.4.x. Most people appear to be using jdbc 1 drivers that do not support xa transactions. In this case you wrap your Driver class with the XADataSourceImpl.java, the driver to use being determined by the jdbc url. (you still don't get xa semantics, but your transactions are committed by jboss). If you have an XADataSource (such as some Oracle drivers), you can use it directly in the XADataSourceLoader. The sharing semantics of jdbc 1 and xa connections/transactions are quite different from one another and I have been unsuccessful in figuring out how XADataSourceLoader deals with this. In jboss 3, all db access is via wrapping jdbc drivers and XADataSources in jca resource adapters. All these mbeans are gone from 3.0. I think it's a lot simpler. The different semantics for the different tx types are clearly expressed in different code. david jencks > > > -Kris > please lose the html _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
