When is later?

You can NOT ever access a persistence context after an exception. RuntimeException is FATAL and NOT recoverable gracefully. This is covered in any documentation on the subject.

And the same is true for a rolled back Exception (@ApplicationException marked rollback). The state of the persistence context is undefined at that point.

An Exception is an exceptional case. It should not be abused for control flow. Write program logic that does not result in exceptions or rely on exceptions for the correct flow of instructions.

Alessandro Lazarotti wrote on Mar 31, 2008 10:23 PM:


I do not use exceptions to control flow.  I to build a filter to remain on the same page (the Seam does not offer it):

This is a contradiction. Of course that is control flow. On the other hand, rolling back transactions is not part of the regular flow of the application. It's an exceptional case used to handle fatal application errors in a graceful fashion.

All applications have Domain Exceptions ... it's normal to interact with incorrect values placed by users.

You do not handle incorrect values by throwing them against the database, see what sticks, and then roll back the transaction if it didn't work. You check before. This is called validation.

The problem is the rollback, not the application exception. The rollback says handle this like a RuntimeException to the persistence provider. Which means it kills the persistence context.

If I have a Domain Exception, my object in conversation lost your association objects? This seems correct?

I don't understand that sentence.