Connections and transactions

Question

Hi all,
I need advice on managing transactions across multiple persistent objects. Currently we have a number of objects that can save their state to the database: they open a connection, perform insert/update, then close the connection:
class PersistentObject
public void store()
// get connection from pool
Connection conn = ConnectionMgr.getConnection();
// do insert/update
// Return connection to pool
conn.close();
We are using Tomcat's built-in connection pool, so ConnectionMgr simply encapsulates the JNDI lookup followed by a call to DataSource.getConnection().
Now we need to be able to store two or more objects in one transaction, something like this:
try {
// begin transaction
object1.store();
object2.store();
// commit
} catch( SQLException ex ) {
// rollback
Problem is that a transaction requires multiple SQL calls to use the same Connection.One way to do this, of course, is to open the connection externally and pass it to each object. However, ideally, it should be more implicit. Ideally, if the transaction is in progress when object2 tries to get connection, it should receive the same one that object1 used. Is there any way to do it? (Well, I can think of one: binding a connection to a session, but I also see a number of disadvatages of that approach).
thanks in advace,
CodeSlinger

Answer 1

this is what i know. Can you not use JTS? With weblogic app server you can use the weblogic.jdbc.jts.Driver to get a connection. Then you can start a transaction and have calls to multiple components say A, B and C. Each component closes the connection when done but the next component gets the same connection if in same execute thread. The connection is returned to pool only when you commit/rollback and all components are in the same transaction. I hope this helps. You should have similar thing with Tomcat.