This may be a silly question, but bare with me. Is it possible to have an extended persistence context without using an EntityManager (rather a native Hibernate Session)? By that, I mean that you can retrieve an object, render the view, and on postback, the following will still be true, because the previous Session is restored. conversationScopedObject == session.get(conversationScopedObject.getId()); The reason I ask is because I am trying to get an understanding of what Seam/EJB 3 provides that Seam/Hibernate does not. I want to avoid using a detached object to do basic CRUD, and to do so I would imagine that the best way is to use the extended persistence context (otherwise known as session-per-conversation pattern). I don't want to go hacking up a solution. I am interested to know if this is something that is supported by Seam without EJB 3. If it isn't, then I will understand why EJB 3 is necessary. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029126#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...