Hey,

I understand that the entity manager is in fagile state,during hibernate callback, so you are not allowed to do some things.

I need to run some queried during pre-remove callback.
The queries need to be based on the current context. they need to check some condition?

Is it ok to do this?

did you try doing that??? were u successful?

it wotk, but in some other scenario (more complicated) it didnt work.
another issue with this is when the callback call from cascade.

I asked a similar sort of question in this topic: http://forums.hibernate.org/viewtopic.php?t=986784

The book basically says you can't use the EM during a callback, by definition of the standard.
The same restriction exists for the traditional Hibernate Session, but the workaround is pretty easy.

As, you can see from the topic though - I've no idea how to create a new EntityManager on the same connection. At the moment, my workaround is just to drop back to using a brand new Hibernate Session. It's a bit dodgy though, swapping from JPA API and back to the Hibernate API just because I can't figure out how to create an EM.

Indeed, interacting with the existing entity manager during a callback isn't allowed. A new session would just create a new connection, which is separate from the callback, and may have its own callback.

-Cameron

That's the trick, you don't let the new session create a new JDBC connection, you create a new session wrapped around the old connection from the original session. Works fine, I've just gotta figure out how to do it with an EnitityManager instead of a HB Session.

Thanks for your answer.
Can you please show how you did it with EM. i work in J2ee mode (with jboss4.2).

Any way it will not solve my problem, because i need to for each entity that are going to be deleted to execute query against the DB, but if you are in another EM than the result might not be as you expected since the first EM didnt execute flush and during cascade you cannot call to flush.

Thank you