Hibernate Configuration

[zenig.szimmerman.sunshineradiology.com]

Any ideas on what could be causing this warning?

WARN  org.jboss.seam.Component  - Exception calling component @Destroy method: serviceTableBean
javax.el.ELException: java.lang.IllegalStateException: EntityManager is closed

components.xml:

<persistence:entity-manager-factory name="entityManagerFactory" persistence-unit-name="myDatabasePU" />
<persistence:managed-persistence-context name="entityManager" auto-create="true" entity-manager-factory="#{entityManagerFactory}" />
<factory name="session" scope="STATELESS" auto-create="true" value="#{entityManager.delegate}" />

ServiceTableBean.java:

@Name("serviceTableBean")
public class ServiceTableBean implements Serializable {
    @In
    private Session session;

    ...
}

I do not explicitly call session.close().  Is it because I am using a STATELESS entityManager delegate?  Should I be using a Seam-managed Hibernation session instead since I am using Hibernate as my JPA?

How can I troubleshoot this?

Thanks,
Shawn

[zenig.szimmerman.sunshineradiology.com]

I am using Seam 2.2.0GA on Glassfish 2.1.1. The Hibernate version is the standard provided within Seam 2.2.0GA.

[zenig.szimmerman.sunshineradiology.com]

I changed the scope to Page and it seems to be doing the trick.

@Name("serviceTableBean")
@Scope(ScopeType.PAGE)
public class ServiceTableBean implements Serializable {
    @In
    private Session session;

    ...
}

But, still leaves the question, should I use the JPA delegate for a session or should I use the Seam-managed Hibernate session?

[zenig.szimmerman.sunshineradiology.com]

I am sure this didn't help: here.  I added the @BypassInterceptors on the @Remove methods of the Event scoped beans that inject the Session.

[zenig.szimmerman.sunshineradiology.com]

I have decided to move towards the Seam-managed Hibernate session long-term.  I am having an issue setting it up seen here: here.