[javaee-spec users] [jsr342-experts] Re: Transactional interceptors and exceptions

From: Linda DeMichiel <>
Date: Tue, 10 Jan 2012 12:40:44 -0800

On 1/10/2012 12:24 PM, Jeff Genender wrote:
> For a worst case scenario, I think marking them for rollback is best (just to be safe). I am not convinced about the
> annotation because what is this needs to be decided at runtime?

The application can always invoke setRollbackOnly in any case. (I'm not sure I'm following you though....)

> Was there any thought to a transaction marking bean attribute in the exception so it could be handled at runtime as
> well? Although testing a parent class could work, it doesn't alleviate the ability to be semi generic on deciding
> whether as an interceptor to flag the transaction as a rollback or not. I think a flag could do the trick pretty nicely.

I'm not following you here. Could you expand upon this to clarify?



> Jeff
> On Jan 10, 2012, at 1:14 PM, Linda DeMichiel wrote:
>> class with @DontRollbackTransaction (real name for this exception *TBD*).