Re: Exceptions thrown from callbacks

[Craig L Russell]

Ah, the perils of spec-writing...

On Feb 1, 2007, at 3:55 PM, Dain Sundstrom wrote:

On Feb 1, 2007, at 3:27 PM, Patrick Linskey wrote:

3.5.6:

"Lifecycle callback methods may throw runtime exceptions. A runtime

methods will be invoked after a runtime exception is thrown."

exception thrown by a callback method that executes within a transaction causes that transaction to be rolled back. No further lifecycle callback

One other thing to check is if the tx is marked rollback only, should we not call anymore lifecycle events or is that "No Further lifecycle callback" clause supposed to apply to the single entity that failed.

More decisions. Is it









5. The provider decides what to do

6. Something else

Craig Russell
DB PMC
[EMAIL PROTECTED] http://db.apache.org/jdo

1. After a runtime exception is thrown (during any em method call) the tx is marked for rollback and no callbacks are called on any entity for any method 2. After a runtime exception is thrown from a user-defined callback, the tx is marked for rollback and no callbacks are called on any entity for any method 3. After a runtime exception is thrown from a user-defined callback, the tx is marked for rollback and no callbacks are called on the entity that stimulated the exception 4. After a runtime exception is thrown from a user-defined callback, the tx is marked for rollback and no callbacks are called on any entity during the execution of the current entity manager method

smime.p7s
Description: S/MIME cryptographic signature