Can we still use loader-repository to scope deployments and override server classes in EAP 5?
Issue
- If we find a conflict between the jars present in an ear and those in the as, is it a valid solution to use the following type of configuration in jboss-app.xml discussed here:
<jboss-app>
<loader-repository>
com.example:archive=unique-archive-name
<loader-repository-config>
java2ParentDelegation=false
</loader-repository-config>
</loader-repository>
</jboss-app>
Environment
Red Hat JBoss Enterprise Application Platform (EAP)
- 5.0.0.GA
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
