R
Richard Huddleston
I'm implementing the Java Content Repository API, and part of it
requires that a specific action occur "after the transaction commits".
I can handle the case when I'm managing the java.sql.Connection
transaction boundries myself, but in a j2ee context I'm running into a bug.
In j2ee, the TransactionManager could / would be managing the
transaction boundries. It appears as though the only way I can be
notified of a transaction boundry is using the SessionSynchronization
interface on an EJB. Is there any other way?
I'm running on j2se 1.5 and j2ee 1.4
-Rich
requires that a specific action occur "after the transaction commits".
I can handle the case when I'm managing the java.sql.Connection
transaction boundries myself, but in a j2ee context I'm running into a bug.
In j2ee, the TransactionManager could / would be managing the
transaction boundries. It appears as though the only way I can be
notified of a transaction boundry is using the SessionSynchronization
interface on an EJB. Is there any other way?
I'm running on j2se 1.5 and j2ee 1.4
-Rich