we use JDBC transaction( not JTA) its work with only single connection.suppose in a connection pooling architecture different connection created according to the client request.in this situation JDBC transaction failed to fulfill the job i am right?.
Judge a man by his questions rather than his answers --Voltaire
SCJP 1.5 97%
posted 8 years ago
A JDBC transaction is controlled by the transaction manager of the DBMS. It has built-in support for transactions but is limited to a single data source (in practice, a single database in most cases).
A non-JDBC transaction is controlled by the transaction manager of the J2EE server. When you use connection pooling, the server will typically require the data source to be created (with the associated connection pool) and bound into its JNDI tree. The server has control of the data source and the connections is therefore able to manage transactions.
I won't say that "JDBC transaction failed to fulfill the job", it is just a case of which service is appropriate for what you want to achieve.