[
https://issues.jboss.org/browse/AS7-5281?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-5281:
-----------------------------------
Stuart, thanks for explaining. :)
Great idea about adding the adapter as a resource root, I'll give that a shot in
JPADependencyProcessor where we have some code that does something similar (I think that
you helped me with that before).
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira