1:40 p.m.
Ales Justin [http://community.jboss.org/people/alesj] created the discussion
"Re: How to stop my WAR loading JBoss's provided 3rd party classes?"
To view the discussion, visit: http://community.jboss.org/message/578803#578803
--------------------------------------------------------------
And yes, I too think that parent-first is more natural, but the
weirdness here is that "plain default" is false while adding classloading config
turns it automatically into true.
Well, the "plain default" knows about
deployment type:
* ear --> isolation --> look locally first == parent-first=false
* war, which has parent-first=false by default
Whereas jb-cl-domain.xml is deployment type agnostic, hence uses the more natural
default.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/578803#578803]
Start a new discussion in JBoss Microcontainer at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
2:49 p.m.
Chris Council [http://community.jboss.org/people/chriscouncil] created the discussion
"Re: How to stop my WAR loading JBoss's provided 3rd party classes?"
To view the discussion, visit: http://community.jboss.org/message/578811#578811
--------------------------------------------------------------
So I'm having a similar issue to Petr, I'm getting the following exception when I
try to start up JBoss with my war in the server/default/deploy directory:
Caused by: org.hibernate.AnnotationException: java.lang.NoSuchMethodException:
org.hibernate.validator.ClassValidator.<init>(java.lang.Class,
java.util.ResourceBundle, org.hibernate.validator.MessageInterpolator, java.util.Map,
org.hibernate.annotations.common.reflection.ReflectionManager)
at
org.hibernate.cfg.Configuration.applyHibernateValidatorLegacyConstraintsOnDDL(Configuration.java:1651)
[:3.6.0.Final]
at org.hibernate.cfg.Configuration.applyConstraintsToDDL(Configuration.java:1623)
[:3.6.0.Final]
at org.hibernate.cfg.Configuration.secondPassCompile(Configuration.java:1415)
[:3.6.0.Final]
at org.hibernate.cfg.Configuration.buildMappings(Configuration.java:1345) [:3.6.0.Final]
Caused by: org.hibernate.AnnotationException:
java.lang.NoSuchMethodException:
org.hibernate.validator.ClassValidator.<init>(java.lang.Class,
java.util.ResourceBundle, org.hibernate.validator.MessageInterpolator, java.util.Map,
org.hibernate.annotations.common.reflection.ReflectionManager)
at
org.hibernate.cfg.Configuration.applyHibernateValidatorLegacyConstraintsOnDDL(Configuration.java:1651)
[:3.6.0.Final]
at org.hibernate.cfg.Configuration.applyConstraintsToDDL(Configuration.java:1623)
[:3.6.0.Final]
at org.hibernate.cfg.Configuration.secondPassCompile(Configuration.java:1415)
[:3.6.0.Final]
...
Note that I'm using JPA 2.0/Hibernate 3.6.0.Final*.* I have a fairly simple project -
in my case, it's just a war. It's a stock JBoss 6.0.0.Final install - all I've
done is put my war, together with an associated db-ds.xml file, into the
server/default/deploy directory. I'm also using Spring 3.0.5.
Here's the relevant section of my project's pom.xml:
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate-entitymanager</artifactId>
<version>3.6.0.Final</version>
<exclusions>
<exclusion>
<groupId>javax.transaction</groupId>
<artifactId>jta</artifactId>
</exclusion>
</exclusions>
</dependency>
I have also tried changing the scope of hibernate-entitymanager to "provided*"*,
in which case my project should be using JBoss 6's provided hibernate libraries, but
when I do that I get this exception:
Caused by: java.lang.IncompatibleClassChangeError: Class
org.hibernate.ejb.HibernatePersistence does not implement the requested interface
javax.persistence.spi.PersistenceProvider
at
org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.createNativeEntityManagerFactory(LocalContainerEntityManagerFactoryBean.java:225)
[:3.0.5.RELEASE]
at
org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.afterPropertiesSet(AbstractEntityManagerFactoryBean.java:308)
[:3.0.5.RELEASE]
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1477)
[:3.0.5.RELEASE]
I have also tried removing the hibernate libraries from $JBOSS_HOME/common/lib, but then
the server immediately halts with this exception:
13:37:45,775 INFO [AbstractServer] Starting: JBossAS [6.0.0.Final
"Neo"]
13:37:47,530 INFO [ServerInfo] Java version: 1.6.0_22,Apple Inc.
13:37:47,530 INFO [ServerInfo] Java Runtime: Java(TM) SE Runtime Environment (build
1.6.0_22-b04-307-10M3261)
13:37:47,530 INFO [ServerInfo] Java VM: Java HotSpot(TM) 64-Bit Server VM
17.1-b03-307,Apple Inc.
13:37:47,530 INFO [ServerInfo] OS-System: Mac OS X 10.6.5,x86_64
13:37:47,531 INFO [ServerInfo] VM arguments: -Xms128m -Xmx512m -XX:MaxPermSize=256m
-Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000
-Dsun.rmi.dgc.server.gcInterval=3600000 -Dprogram.name=run.sh
-Djava.library.path=/wdev/jboss-6.0.0.Final/bin/native/lib64
-Djava.endorsed.dirs=/wdev/jboss-6.0.0.Final/lib/endorsed
13:37:47,620 INFO [JMXKernel] Legacy JMX core initialized
13:37:52,790 ERROR [AbstractKernelController] Error installing to PreInstall:
name=CEMFBuilder state=Real: java.lang.NoClassDefFoundError:
javax/persistence/spi/PersistenceUnitInfo
at java.lang.Class.getDeclaredMethods0(Native Method) [:1.6.0_22]
at java.lang.Class.privateGetDeclaredMethods(Class.java:2427) [:1.6.0_22]
at java.lang.Class.getDeclaredMethods(Class.java:1791) [:1.6.0_22]
I've tried using this jboss-classloading-domain.xml in my WEB-INF directory, but it
seems to have no effect:
<?xml version="1.0" encoding="UTF-8"?>
<classloading-domain xmlns="urn:jboss:classloading-domain:1.0"
name="MyDomain">
<parent-policy>
<before-filter>
<javabean xmlns="urn:jboss:javabean:2.0"
class="org.jboss.classloader.plugins.filter.NegatingClassFilter">
<constructor>
<parameter>
<javabean xmlns="urn:jboss:javabean:2.0"
class="org.jboss.classloader.spi.filter.RecursivePackageClassFilter">
<constructor>
<parameter>org.hibernate</parameter>
</constructor>
</javabean>
</parameter>
</constructor>
</javabean>
</before-filter>
</parent-policy>
</classloading-domain>
I do get further when I remove *just* the hibernate-validator-legacy.jar from common/lib -
but I really don't want to modify the stock JBoss installation.
Any thoughts?
Thanks in advance.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/578811#578811]
Start a new discussion in JBoss Microcontainer at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
3:10 p.m.
Petr H [http://community.jboss.org/people/hostalp] created the discussion
"Re: How to stop my WAR loading JBoss's provided 3rd party classes?"
To view the discussion, visit: http://community.jboss.org/message/578814#578814
--------------------------------------------------------------
Chris: based on my findings you can currently either remove that
hibernate-validator-legacy.jar which will put it back to work, or do something like:
<?xml version="1.0" encoding="UTF-8"?>
<classloading-domain xmlns="urn:jboss:classloading-domain:1.0"
name="jboss.j2ee:extension=LoaderRepository,service=EARDeployment,url='myapp.ear'"
parent-domain="DefaultDomain">
<parent-policy>
<before-filter>
<javabean xmlns="urn:jboss:javabean:2.0"
class="org.jboss.classloader.plugins.filter.NegatingClassFilter">
<constructor>
<parameter>
<javabean xmlns="urn:jboss:javabean:2.0"
class="org.jboss.classloader.spi.filter.RecursivePackageClassFilter">
<constructor>
<parameter>org.hibernate.validator</parameter>
</constructor>
</javabean>
</parameter>
</constructor>
</javabean-->
</before-filter>
<after-filter>
<javabean xmlns="urn:jboss:javabean:2.0"
class="org.jboss.classloader.plugins.filter.NegatingClassFilter">
<constructor>
<parameter>
<javabean xmlns="urn:jboss:javabean:2.0"
class="org.jboss.classloader.spi.filter.RecursivePackageClassFilter">
<constructor>
<parameter>org.hibernate.validator</parameter>
</constructor>
</javabean>
</parameter>
</constructor>
</javabean>
</after-filter>
</parent-policy>
</classloading-domain>
where you'll have to replace the domain name with the one valid for your case (you can
find it via jmx-console for example).
But that will introduce the currently discussed change in classloadin behavior - plain war
is parent-first=false while with jboss-classloading-domain.xml it will change to
parent-first=true (and it's not that simple to switch it back while preserving the
required package filters) which may (but maybe it won't) cause you some troubles.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/578814#578814]
Start a new discussion in JBoss Microcontainer at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
3:13 p.m.
Ales Justin [http://community.jboss.org/people/alesj] created the discussion
"Re: How to stop my WAR loading JBoss's provided 3rd party classes?"
To view the discussion, visit: http://community.jboss.org/message/578816#578816
--------------------------------------------------------------
Caused by: org.hibernate.AnnotationException:
java.lang.NoSuchMethodException:
org.hibernate.validator.ClassValidator.<init>(java.lang.Class,
java.util.ResourceBundle, org.hibernate.validator.MessageInterpolator, java.util.Map,
org.hibernate.annotations.common.reflection.ReflectionManager)
at
org.hibernate.cfg.Configuration.applyHibernateValidatorLegacyConstraintsOnDDL(Configuration.java:1651)
[:3.6.0.Final]
at org.hibernate.cfg.Configuration.applyConstraintsToDDL(Configuration.java:1623)
[:3.6.0.Final]
at org.hibernate.cfg.Configuration.secondPassCompile(Configuration.java:1415)
[:3.6.0.Final]
at org.hibernate.cfg.Configuration.buildMappings(Configuration.java:1345) [:3.6.0.Final]
> Caused by: org.hibernate.AnnotationException: java.lang.NoSuchMethodException:
org.hibernate.validator.ClassValidator.<init>(java.lang.Class,
java.util.ResourceBundle, org.hibernate.validator.MessageInterpolator, java.util.Map,
org.hibernate.annotations.common.reflection.ReflectionManager)
> at
org.hibernate.cfg.Configuration.applyHibernateValidatorLegacyConstraintsOnDDL(Configuration.java:1651)
[:3.6.0.Final]
> at org.hibernate.cfg.Configuration.applyConstraintsToDDL(Configuration.java:1623)
[:3.6.0.Final]
> at org.hibernate.cfg.Configuration.secondPassCompile(Configuration.java:1415)
[:3.6.0.Final]
> ...
Note that I'm using JPA 2.0/Hibernate 3.6.0.Final*.* I have a fairly simple project -
in my case, it's just a war. It's a stock JBoss 6.0.0.Final install - all I've
done is put my war, together with an associated db-ds.xml file, into the
server/default/deploy directory. I'm also using Spring 3.0.5.
Here's the relevant section of my project's pom.xml:
> <dependency>
> <groupId>org.hibernate</groupId>
> <artifactId>hibernate-entitymanager</artifactId>
> <version>3.6.0.Final</version>
> <exclusions>
> <exclusion>
> <groupId>javax.transaction</groupId>
> <artifactId>jta</artifactId>
> </exclusion>
> </exclusions>
> </dependency>
>
I have also tried changing the scope of hibernate-entitymanager to
"provided*"*, in which case my project should be using JBoss 6's provided
hibernate libraries, but when I do that I get this exception:
> Caused by: java.lang.IncompatibleClassChangeError: Class
org.hibernate.ejb.HibernatePersistence does not implement the requested interface
javax.persistence.spi.PersistenceProvider
> at
org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.createNativeEntityManagerFactory(LocalContainerEntityManagerFactoryBean.java:225)
[:3.0.5.RELEASE]
> at
org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.afterPropertiesSet(AbstractEntityManagerFactoryBean.java:308)
[:3.0.5.RELEASE]
> at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1477)
[:3.0.5.RELEASE]
Hmmm, how can this happen if both you and JBossAS use the same Hibernate version?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/578816#578816]
Start a new discussion in JBoss Microcontainer at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
3:16 p.m.
Ales Justin [http://community.jboss.org/people/alesj] created the discussion
"Re: How to stop my WAR loading JBoss's provided 3rd party classes?"
To view the discussion, visit: http://community.jboss.org/message/578817#578817
--------------------------------------------------------------
> Here's the relevant section of my project's pom.xml:
>
> > <dependency>
> > <groupId>org.hibernate</groupId>
> > <artifactId>hibernate-entitymanager</artifactId>
> > <version>3.6.0.Final</version>
> > <exclusions>
> > <exclusion>
> > <groupId>javax.transaction</groupId>
> > <artifactId>jta</artifactId>
> > </exclusion>
> > </exclusions>
> > </dependency>
> >
>
> I have also tried changing the scope of hibernate-entitymanager to
"provided*"*, in which case my project should be using JBoss 6's provided
hibernate libraries, but when I do that I get this exception:
>
> > Caused by: java.lang.IncompatibleClassChangeError: Class
org.hibernate.ejb.HibernatePersistence does not implement the requested interface
javax.persistence.spi.PersistenceProvider
> > at
org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.createNativeEntityManagerFactory(LocalContainerEntityManagerFactoryBean.java:225)
[:3.0.5.RELEASE]
> > at
org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.afterPropertiesSet(AbstractEntityManagerFactoryBean.java:308)
[:3.0.5.RELEASE]
> > at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1477)
[:3.0.5.RELEASE]
>
Hmmm, how can this happen if both you and JBossAS use the same Hibernate version?
This would mean that somehow JPA slips into your project, hence those JPA classes
get used -- as by the servlet spec.
Otoh, JBoss' Hibernate of course doesn't use those JPA classes, but its own.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/578817#578817]
Start a new discussion in JBoss Microcontainer at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
3:35 p.m.
Chris Council [http://community.jboss.org/people/chriscouncil] created the discussion
"Re: How to stop my WAR loading JBoss's provided 3rd party classes?"
To view the discussion, visit: http://community.jboss.org/message/578821#578821
--------------------------------------------------------------
Ales Justin wrote:
Hmmm, how can this happen if both you and JBossAS use the same Hibernate version?
That's confusing to me, too. When I build my war using the default "compile"
scope I have these jars inside WEB-INF/lib:
hibernate-commons-annotations-3.2.0.Final.jar
hibernate-core-3.6.0.Final.jar
hibernate-entitymanager-3.6.0.Final.jar
hibernate-jpa-2.0-api-1.0.0.Final.jar
hibernate-commons-annotations-3.2.0.Final.jar
hibernate-core-3.6.0.Final.jar
hibernate-entitymanager-3.6.0.Final.jar
hibernate-jpa-2.0-api-1.0.0.Final.jar
I've verified that those jars are *not* in my war when I build using the
"provided" scope.
These versions seem to be the same as in the JBoss distribution. The only one that's
different is hibernate-commons-annotations, which is "6.0.0.Final" in the
manifest. (It would be nice if the libs in $JBOSS_HOME/common/lib would have the version
numbers as part of the filename, so I didn't have to go into each one and look at the
manifest to determine what versions they are!)
I did find this kind of interesting:
$ ls -l /appserver/jboss-6.0.0.Final/common/lib/hibernate-core.jar
-rw-rw-r--@ 1 chriscouncil staff 3116797 Dec 28 08:30
/wdev/jboss-6.0.0.Final/common/lib/hibernate-core.jar
$ ls -l /m2repo/org/hibernate/hibernate-core/3.6.0.Final/hibernate-core-3.6.0.Final.jar
-rw-r--r-- 1 chriscouncil staff 3083100 Oct 14 16:22
/mm/org/hibernate/hibernate-core/3.6.0.Final/hibernate-core-3.6.0.Final.jar
My hibernate jars come from the jboss public repo at
https://repository.jboss.org/nexus/content/repositories/public
https://repository.jboss.org/nexus/content/repositories/public, so I'd expect them to
be the same size. Obviously the MD5 sums don't match ;) I haven't checked any
further, though.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/578821#578821]
Start a new discussion in JBoss Microcontainer at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
4:08 p.m.
Chris Council [http://community.jboss.org/people/chriscouncil] created the discussion
"Re: How to stop my WAR loading JBoss's provided 3rd party classes?"
To view the discussion, visit: http://community.jboss.org/message/578829#578829
--------------------------------------------------------------
So I did have a JPA jar (+org.hibernate.java-persistence:jpa-api:++2.0-cr-1+) in my war,
coming from a transitive dependency. After removing it (and the four hibernate jars
+hibernate-commons-annotations-3.2.0.Final.jar, hibernate-core-3.6.0.Final.jar,
hibernate-entitymanager-3.6.0.Final.jar, hibernate-jpa-2.0-api-1.0.0.Final.jar+), I got
the following exception on startup:
Caused by: java.lang.IllegalArgumentException: Can't find a persistence unit named
'null' in
AbstractVFSDeploymentContext@1032284510{vfs:///wdev/jboss-6.0.0.Final/server/default/deploy/properties-webapp-0.0.1-SNAPSHOT.war}
at
org.jboss.jpa.resolvers.BasePersistenceUnitDependencyResolver.resolvePersistenceUnitSupplier(BasePersistenceUnitDependencyResolver.java:107)
[:1.0.2-alpha-3]
at
org.jboss.web.deployers.AbstractWarDeployer.deployWebModule(AbstractWarDeployer.java:793)
[:6.0.0.Final
Caused by: java.lang.IllegalArgumentException: Can't find a
persistence unit named 'null' in
AbstractVFSDeploymentContext@1032284510{vfs:///appserver/jboss-6.0.0.Final/server/default/deploy/my-webapp-0.0.1-SNAPSHOT.war}
at
org.jboss.jpa.resolvers.BasePersistenceUnitDependencyResolver.resolvePersistenceUnitSupplier(BasePersistenceUnitDependencyResolver.java:107)
[:1.0.2-alpha-3]
at
org.jboss.web.deployers.AbstractWarDeployer.deployWebModule(AbstractWarDeployer.java:793)
[:6.0.0.Final]
So the only way I can get things to work right now is to have those four jars inside my
war, and hibernate-validator-legacy.jar manually removed from common/lib.
Oh well. I don't really want to remove the hibernate jars from my war, because then it
won't work on Glassfish and Jetty.
Any thoughts on why JBoss won't start up without the hibernate jars in common/lib? It
seems like there could be problems if I upgrade the war to another version of Hibernate in
the future, and if I'm going to be modifying common/lib anyway, maybe I should just
remove Hibernate altogether... or alternatively, ensure that the version I want is in that
directory.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/578829#578829]
Start a new discussion in JBoss Microcontainer at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
5057
days inactive
5057
days old
6 comments
3 participants
participants (3)
-
Ales Justin -
Chris Council
-
Petr H