[jboss-user] [JBoss Microcontainer] - Re: How to stop my WAR loading JBoss's provided 3rd party classes?

Petr H do-not-reply at jboss.com
Tue Jan 4 16:10:11 EST 2011


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=&apos;myapp.ear&apos;" 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&containerType=14&container=2114]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-user/attachments/20110104/e3d8229d/attachment.html 


More information about the jboss-user mailing list