TX data source and non TX data source

[Monmohan Singh]

In weblogic there are TX data sources and non TX Data sources
If we are using simple select queries, update etc then we donot need to use TX data sources.I believe the TX data source is there when you explicitly want to use transaction for data access.
But does it really harm the perforamce etc when we use TX data source for direct JDBC access where transaction is not needed??

[Pradeep bhatt]

If your application meets any of the following criteria, you should use a TxDataSource in WebLogic Server:

Uses the Java Transaction API (JTA)
Uses the WebLogic Server EJB container to manage transactions
Includes multiple database updates during a single transaction.

[Monmohan Singh]

In case I have a class in ejb container that doen't use ejb container managed transaction and also doesn't uses JTA. What is the problem if I still use a TX data source??Is there a reason I shouldn't be using TX data source

[Lasse Koskela]

No problems. Theoretically, the non-tx JDBC driver might be faster due to some optimizations but you probably won't see any difference in practice.

[Monmohan Singh]

but then I wonder why do you need to provide a non TX data source if it is not faster also?

[Lasse Koskela]

Because then you don't need to implement the transaction management stuff.