[
https://issues.apache.org/jira/browse/GERONIMO-3968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks closed GERONIMO-3968.
----------------------------------
Resolution: Invalid
we don't seem to have cleaned up our schemas sufficiently, but the
context-priority-classloader has been gone since geronimo 1.1.
Rather than just supplying this feature for web apps, you can now force
child-first classloading in any module with the <inverse-classloading/> element
in the environment element which is common to all geronimo plans. In an ee app
client you probably want to specify <inverse-classloading/> in the
client-environment element.
> context-priority-classloader commented :(
> -----------------------------------------
>
> Key: GERONIMO-3968
> URL: https://issues.apache.org/jira/browse/GERONIMO-3968
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: deployment
> Affects Versions: 2.0, 2.0.1, 2.0.2, 2.1
> Reporter: Bruno Braga
> Assignee: David Jencks
> Priority: Blocker
>
> 1) open file http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1
> 2) search for context-priority-classloader
> 3) results: <!--<xs:element name="context-priority-classloader"
> type="xs:boolean" minOccurs="0"/>-->
> COMMENTED?
> The same applies to:
> http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-1.1
> http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0
> http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1
> How to use this parameter?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
