This first preview release of Hibernate EntityManager implements the EJB3 persistence API, entity lifecycle, and query features on top of the Hibernate core. Together with Hibernate Annotations you can now preview and develop on a complete (and standalone) EJB3 persistence solution. Use the JBoss EJB3 Preview if you need a full EJB3 container with enterprise services - Hibernate persistence is included.

Both Hibernate EntityManager and Hibernate Annotations require Hibernate 3.1 and JDK 5.0. If you are not using EJB3 persistence, please continue using Hibernate 3.0.x (with any JDK supported). Please use our forum for questions and feedback.

http://entitymanager.hibernate.org/
http://annotations.hibernate.org/
http://www.jboss.org/products/ejb3

Dear All,

What is the purpose of the new StatelessSession available in Hibernate 3.1 beta 1? Is there going to be an equivalent 'openStatelessSession' in EJB3's EntityManager?

Let us say I am developing a Web application using JSF and EJB3. Typically I would not want any of the objects returned by the EJB3 layer to be associated with a persistence context, as otherwise when I pass them to my JSF layer (which I assume is valid as EJBs are now POJO value objects) and JSF updates them, EJB3 will attempt to serialize them - even though the user may not have clicked 'Save' in the UI (eg. there may be some validation errors, or the user may be in the middle of a 'wizard'-style interaction)

Is this the intent of StatelessSession? To make it easy to use Hibernate's mapping functionality without also having to worry about its lifecycle management capabilities, in situations where the lifecycle is, effectively, being managed by someone else (in this case, JSF).

Or have I gotten the wrong end of this completely?

Many thanks in advance,

Richard.

StatelessSession has been done for non OLTP processing.
Please use another thread for these kind of questions.