Problem using ExtendedPersistenceContext and ApplicationException

I'm trying to use a ExtendedPersistenceContext to implement the detached object pattern using EJB 3 and Seam.

I also have a business rule engine that processes my object when I merge it based on the data on the database.

When something goes wrong in the business rule, the app launches an Exception marked with

@ApplicationException(rollback = true)

Unfortunately, according to the EJB specific and this question from SO Forcing a transaction to rollback on validation errors in Seam, that annotations forces all the object to become detached.

So basically my object is in the same state as before (it contains modification made by the user) but it can't resolve its relations using the ExtendedPersistenceContext, since it's in the Detached state.

This breaks all my page, since I have AJAX calls that I want to resolve even after the failure of the Business Engine.

I can't merge the object 开发者_如何转开发again otherwise the modification will be propagated on the DB, and I don't want to do it if there is an ApplicationException.

I want to rollback the transaction if a business validation fail, but I want my object to be still in a persistent state so that it can resolve its relations using the extended persistence context.

Any suggestion?

To detach a single object can use entityManager.detach(object), else can use entityManager.clear() to detach all underlying objects for a EntityManager.

You can clone the objects to maintain the changes being made & prevent them from rolling back on exception. The changes are to be done on cloned object & then apply them to the managed object before persistence.

If the object is detached, then have to perform entityManager.refresh(object) to make it managed & then applying changes of cloned object accordingly to it.