[jboss-jira] [JBoss JIRA] (AS7-5281) JBoss uses static Hibernate module instead of Hibernate jars included in deployment

[Scott Marlow (JIRA)]

    [ https://issues.jboss.org/browse/AS7-5281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12735018#comment-12735018 ] 

Scott Marlow commented on AS7-5281:
-----------------------------------

Also need Hibernate changes to allow the Region Factory class instance to be passed in instead of the class name (HHH-7708).  We can easily fix HHH-7708 but if we change AS7 to require the HHH-7708 fix, that will prevent AS7 from using earlier versions of Hibernate.  

Another way is to use the RegionFactoryInitiator when that is ready (should be in in next Hibernate ORM minor/major release).
                
> JBoss uses static Hibernate module instead of Hibernate jars included in deployment
> -----------------------------------------------------------------------------------
>
>                 Key: AS7-5281
>                 URL: https://issues.jboss.org/browse/AS7-5281
>             Project: Application Server 7
>          Issue Type: Feature Request
>          Components: Class Loading, JPA / Hibernate
>    Affects Versions: 7.1.1.Final
>         Environment: JBoss 7.1.1.Final & Hibernate 4.1.5.SP1 on Mac OSX 10.7/10.8
> SQL Server 2008 on Windows 7 virtual
>            Reporter: Kuthair Habboush
>            Assignee: Scott Marlow
>              Labels: classloader, hibernate, jboss, persistence.xml
>         Attachments: hibernate-test.zip, persistence.xml
>
>
> JBoss is loading Hibernate 4.0.1.Final (ships with) instead of the version specified in my Maven POM file and embedded in WAR archive, version: 4.1.5.SP1.
> This ONLY occurs when I have a Persistence Unit setup in my WAR file in directory: resources/META-INF.
> If I rename persistence.xml to persistence.xml.old, JBoss loads the correct version: Hibernate 4.1.5.SP1.
> I have a sample project.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira