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/578473#578473
--------------------------------------------------------------
I tried both with bundled Validator and without it, but no
difference. In verbose:class output I could see only loading of certain Validator classes
from common/lib/hibernate-validator.jar and hibernate-validator-legacy.jar.
Validator should be bundled as well.
Also note that even without specifying that filter the Hibernate
3.5.6 was being used so even here there's no difference.One interesting thing is that
we don't actually use the Validator in our app, but it looks like since it's on
the classpath and gets loaded it interfers with the app.
If the Hibernate was/is
part of war' lib/ dir then this makes sense.
If not, then it's strange. :-)
Isn't some sort of jboss-classloading.xml setup required for this
case? I wonder if I don't have to setup an ear level one specifying the MyDomain as
domain and then another in each of the wars specifying the MyDomain as parent domain
(I'm not sure how the domain inheritance works here - if wars inherit the ear domain
as their parent or not).
The war' parent classloader is (unless explicity set
differently) ear' root classloader.
And of course this classloader -- via jboss-classloading-domain.xml -- is in its own
filtered domain
--------------------------------------------------------------
Reply to this message by going to Community
[
http://community.jboss.org/message/578473#578473]
Start a new discussion in JBoss Microcontainer at Community
[
http://community.jboss.org/choose-container!input.jspa?contentType=1&...]