Non-JTS datasource

Question

Dumb questions. What is the exact definition of 'non-JTS datasource'? And what are the recommended usages of the datasource? The TopLink's doc has little information on it. It says "Use Non-JTS for Specify if the session requires a non-JTS connection. Note: Normally, use this option for an application server when using cache synchronization".
We use WAS connection pooling with Oracle databases. Some projects use 'XA datasource' while others use 'non-XA datasource'. In the sessions xml files, we all use <datasource> tag.
What are the differences b/w the 'non-JTS datasource' referenced in TopLink and the 'non-XA datasource' concept?
Also, I was told that all datasources in WAS 5.x are JTS datasources. I haven't found any information on it in the WAS documentations. Anyone has any more info on it?
Thanks a lot for your assistance.
Haiwei

Answer 1

Andrei,
I tried what you suggested, with WAS XA and non-XA datasource. Here is the code:             UserTransaction transaction = (UserTransaction) new InitialContext().lookup(USER_TRANSACTION);
            transaction.begin();
            connection = ((DataSource) new InitialContext().lookup(NON_XA_DATASOURCE)).getConnection("user04", "user04");
            statement = connection.createStatement();
            numberOfRows =
                statement.executeUpdate(
                    "UPDATE USER04.PERSON SET VERSION = VERSION +1 WHERE  ID = '9999'");
            connection.commit();
            transaction.rollback();With XA datasource or non-XA datasource, I was both getting exception (see below), hence the version is not updated.
java.sql.SQLException: DSRA9350E: Operation Connection.commit is not allowed during a global transactionThis seems to suggest (or confirm) that the WAS datasources are JTS datasources.
Any comment?
Haiwie