"davidakoontz" wrote :
| I've also see examples that use this:
|
<loader-respository-config>java2ParentDelegation=false</loader-respository-config>
|
| What does this turn off - how does that effect the class loading for my
EAR? Why don't I find a reference to this in the manuals?
|
It controls the order between parent and child repositories:
Support for specifying custom loader repositories has been extended to SARs,
EJB jars and WARs in addition to EARs. In addition the loader repository
configuration allows for child first class loading rather than the parent
delegation model. This allows deployments to override classes from the server
level. To enable deployment first class loading use a configuration fragment
like:
<loader-repository>
jmx-domain:prop1=value1,prop2=value2,...
<loader-repository-config>java2ParentDelegation=false</loader-repository-config>
</loader-repository>
in the jboss-app.xml, jboss.xml, jboss-web.xml or jboss-service.xml descriptor.
See the corresponding descriptor DTD in the docs/dtd directory for more details.
You should also try the deployment with the latest 3.2.x bug fix release, the
older versions did have known issues with some XML classes "leaking" to
isolated deployments.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3857425#3857425
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3857425
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
