Hello,
i have a stateful session bean, which declares a dependancy on EntityManager:

stateful session bean also declares a dependancy on a stateless DAO. Stateful session bean has method: createEntity:



Stateful bean as you may guess defines a dependancy on a stateless via @EJB. Stateful bean also has a @Remove method (public void submit()) - which flushes entity manager. Similar example is in Java Persistance With Hibernate on pg 727. The stateless is implemented as suggested in the example: stateless extends abstract class GenericEJB3DAO wich defines methods basic to all entities: makePersistent. Here is the caveat: stateless is a @Local bean stateful is remote, when i obtain reference to stateful, first execution of createJobSeeker, followed by submit - persists the entity (although does it in stateless bean not on submit invokation), the following invocation of the same method throws an exception:



Now when i invoke same set of methods in about 1 - 2 minutes, its okay again. Shouldn't the container set my stateless EntityManager with the one in a stateful session bean and not keep the old closed entityManager. This is deployed on glassfish.

Thank you.

Hello,
i forgot to mention an important detail. Here is the problem i got faced with at first:



from preceding stateless everything is legal, except the code is buggy, in a scene that when ever container pooled the stateless it kept the EntityManagerImpl - which was by now closed for sure. Two questions:
1) when i work with session obtained in the followign way (actually thats what i did - having original EntityManager as a type injected the correct one always):



from preceding, will session be automatically managed, by hibernate and be associated with JTA? I don't have to close it or separately create transactions right?

2) calling getDelegate() twice seems repetitive, is that how it is supposed to be?. I bet on JBoss 1 call is enough.

Thank you