[seam-issues] [JBoss JIRA] (JBSEAM-4936) SEAM 2.3 - Spring 3 - Hibernate 4 Integration bug

[Stephane REMI (JIRA)]

Stephane REMI created JBSEAM-4936:
-------------------------------------

             Summary: SEAM 2.3 - Spring 3 - Hibernate 4 Integration bug
                 Key: JBSEAM-4936
                 URL: https://issues.jboss.org/browse/JBSEAM-4936
             Project: Seam 2
          Issue Type: Bug
          Components: Spring
    Affects Versions: 2.3.0.BETA1
         Environment: Windows 7, Tomcat 7.0.20
            Reporter: Stephane REMI


When I try to integrate Seam 2.3.0 Beta1 with Spring 3.1 and Hibernate 4, I've this exception when I access to hibernate current session.

Caused by: java.lang.ClassCastException: org.springframework.orm.hibernate4.SessionHolder cannot be cast to org.springframework.orm.hibernate3.SessionHolder
          at org.springframework.orm.hibernate3.SessionFactoryUtils.doGetSession(SessionFactoryUtils.java:289) ~[spring-orm-3.1.1.RELEASE.jar:3.1.1.RELEASE]
          at org.springframework.orm.hibernate3.SessionFactoryUtils.doGetSession(SessionFactoryUtils.java:258) ~[spring-orm-3.1.1.RELEASE.jar:3.1.1.RELEASE]
          at org.jboss.seam.ioc.spring.SeamManagedSessionFactoryBean$SeamManagedSessionFactoryHandler.invoke(SeamManagedSessionFactoryBean.java:178) ~[jboss-seam-ioc-2.3.0.Beta1.jar:2.3.0.Beta1]
          at $Proxy52.getCurrentSession

If commiters wants more details on configuration, they could find on discussion link below.

I search in "org.jboss.seam.ioc.spring.SeamManagedSessionFactoryBean" at line 178 and I found a dependency to "org.springframework.orm.hibernate3.SessionFactoryUtils". Unfortunately, Spring use "org.springframework.orm.hibernate4.SessionFactoryUtils" to manage Hibernate api 4.x. And I can't return to hibernate 3.x api because Seam 2.3 work only with hibernate api 4.x.
 
Also I think issue resolution is only change import in SeamManagedSessionFactoryBean.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira