[ https://issues.jboss.org/browse/AS7-5281?page=com.atlassian.jira.plugin.s... ] Scott Marlow reassigned AS7-5281: --------------------------------- Assignee: Scott Marlow (was: David Lloyd) -- 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

[ https://issues.jboss.org/browse/AS7-5281?page=com.atlassian.jira.plugin.s... ] Kuthair Habboush commented on AS7-5281: --------------------------------------- Hi Scott, Thanks for your reply. I downloaded "Last Successful Artifact" (jboss-as-7.x.zip) which extracted to folder: jboss-as-7.2.0.Alpha1-SNAPSHOT However, I'm seeing the same problem. When persistence.xml is in place, I get the following output: 16:22:39,577 INFO [stdout] (http-/127.0.0.1:8080-3) org.hibernate: 4.1.4.Final 16:22:39,578 INFO [stdout] (http-/127.0.0.1:8080-3) org.hibernate.ejb: 4.1.4.Final That should be 4.1.5.SP1. Did I download the right zip? Thanks again, -Kuthair -- 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

[ https://issues.jboss.org/browse/AS7-5281?page=com.atlassian.jira.plugin.s... ] Kuthair Habboush edited comment on AS7-5281 at 8/1/12 4:41 PM: --------------------------------------------------------------- Hi Scott, Thanks for your reply. I downloaded "Last Successful Artifact" (jboss-as-7.x.zip) which extracted to folder: jboss-as-7.2.0.Alpha1-SNAPSHOT However, I'm seeing the same problem. When persistence.xml is in place, I get the following output: 16:22:39,577 INFO [stdout] (http-/127.0.0.1:8080-3) org.hibernate: 4.1.4.Final 16:22:39,578 INFO [stdout] (http-/127.0.0.1:8080-3) org.hibernate.ejb: 4.1.4.Final That should be 4.1.5.SP1. Did I download the right zip? Thanks again, -Kuthair PS.. I noticed the persistence.xml file I gave you (in zip) had been auto-formatted by my xml tool which transposed name & value for the dialect. This won't deploy as is. I'm attaching another persistence.xml file. was (Author: sshtac): Hi Scott, Thanks for your reply. I downloaded "Last Successful Artifact" (jboss-as-7.x.zip) which extracted to folder: jboss-as-7.2.0.Alpha1-SNAPSHOT However, I'm seeing the same problem. When persistence.xml is in place, I get the following output: 16:22:39,577 INFO [stdout] (http-/127.0.0.1:8080-3) org.hibernate: 4.1.4.Final 16:22:39,578 INFO [stdout] (http-/127.0.0.1:8080-3) org.hibernate.ejb: 4.1.4.Final That should be 4.1.5.SP1. Did I download the right zip? Thanks again, -Kuthair -- 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

[ https://issues.jboss.org/browse/AS7-5281?page=com.atlassian.jira.plugin.s... ] Scott Marlow commented on AS7-5281: ----------------------------------- The code in org.jboss.as.jpa.processor.PersistenceProviderHandler.deploy() that normally loads the persistence provider included in the deployment, is seeing the static Hibernate module instead. {code} final Class<? extends PersistenceProvider> providerClass = deploymentModuleClassLoader.loadClass(providerName).asSubclass(PersistenceProvider.class); final Constructor<? extends PersistenceProvider> constructor = providerClass.getConstructor(); provider = constructor.newInstance(); // provider.getClass().getClassLoader() == "Module org.hibernate:main" {code} -- 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

[ https://issues.jboss.org/browse/AS7-5281?page=com.atlassian.jira.plugin.s... ] Stuart Douglas edited comment on AS7-5281 at 8/2/12 9:11 PM: ------------------------------------------------------------- This is the expected behaviour. Depending on what you are trying to do there are a few solutions. Iy you simply want to use hibernate with no container integrations at all you can add the following jboss-deployment-structure.xml {code} <jboss-deployment-structure> <deployment> <exclude-subsystems> <subsystem name="jpa" /> </exclude-subsystems> </deployment> </jboss-deployment-structure> {code} was (Author: swd847): This is the expected behaviour. Depending on what you are trying to do there are a few solutions. Iy you simply want to use hibernate with no container integrations at all you can add the following jboss-deployment-structure.xml {code} <jboss-deployment-structure> <deployment> <exclude-subsystems> <subsystem name="resteasy" /> </exclude-subsystems> </deployment> </jboss-deployment-structure> {code} -- 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

[ https://issues.jboss.org/browse/AS7-5281?page=com.atlassian.jira.plugin.s... ] Scott Marlow commented on AS7-5281: ----------------------------------- I don't think we can currently expect the packaged Hibernate 4.x jars to work since the Hibernate integration adapter module (org.jboss.as.jpa.hibernate:4) is associated with the static Hibernate module. http://pastebin.com/u8dxU25Q shows the error that occurs when the org.jboss.as.jpa.hibernate:4 (which has the static Hibernate module on its classpath) adapter is used with the packaged Hibernate jars. One of the other solutions is mentioned [here.|https://docs.jboss.org/author/display/AS71/JPA+Reference+Guide#JPAR...] -- 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

[ https://issues.jboss.org/browse/AS7-5281?page=com.atlassian.jira.plugin.s... ] Scott Marlow resolved AS7-5281. ------------------------------- Resolution: Rejected Stuart is right, we cannot easily support this now (since its not practical for deployments to also include their own Hibernate integration adapter (equivalent of the org.jboss.as.jpa.hibernate:4 module). -- 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

[ https://issues.jboss.org/browse/AS7-5281?page=com.atlassian.jira.plugin.s... ] Kuthair Habboush edited comment on AS7-5281 at 8/3/12 12:18 PM: ---------------------------------------------------------------- That exclusion seems to work, but just a note for anyone else that maybe watching: <exclude-subsystems> is not supported in JBoss AS 7.1.1.Final. Thank you guys, for your time. was (Author: sshtac): That exclusion seems to work, but <exclude-subsystems> is not supported in JBoss AS 7.1.1.Final. Thank you for your time. -- 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

[ https://issues.jboss.org/browse/AS7-5281?page=com.atlassian.jira.plugin.s... ] Kuthair Habboush commented on AS7-5281: --------------------------------------- Thanks Scott, we've tried that and it definitely works. -- 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

[ 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). -- 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

[ https://issues.jboss.org/browse/AS7-5281?page=com.atlassian.jira.plugin.s... ] Scott Marlow commented on AS7-5281: ----------------------------------- Issue 1. The Hibernate adapter module has a 1-1 bi-directional dependency on the Hibernate module. Issue 2. The Hibernate adapter also has dependencies on other AS modules. As a test, I copied the Hibernate adapter jar into the deployment and also set: {quote}(also set <property name="jboss.as.jpa.providerModule" value="application"/> <property name="jboss.as.jpa.adapterClass" value="org.jboss.as.jpa.hibernate4.HibernatePersistenceProviderAdaptor"/>) {quote} Which got us to the next dependency issue: {quote}java.lang.ClassNotFoundException: org.jboss.as.controller.descriptions.DescriptionProvider from [Module "deployment.wartest_hiber4.war:main" {quote} We need to separate the management console code out of the Hibernate adapter. -- 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

[ https://issues.jboss.org/browse/AS7-5281?page=com.atlassian.jira.plugin.s... ] 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). -- 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