[
https://issues.apache.org/jira/browse/GERONIMO-3914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12828050#action_12828050
]
Jean-Jacques Parent commented on GERONIMO-3914:
-----------------------------------------------
Quite old, out of date. I close it
> Use of hidden classes
> ---------------------
>
> Key: GERONIMO-3914
> URL: https://issues.apache.org/jira/browse/GERONIMO-3914
> Project: Geronimo
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: core
> Affects Versions: 2.0.1
> Reporter: Jean-Jacques Parent
>
> First of all, thank you for your quick reply.
> We have applied your solution and it works now. We encoutered some similar
> problems, which were also due to jar conflicts. So we had to add another
> hidden class as follow :
> <hidden-classes>
> <filter>org.jaxen</filter>
> <filter>org.apache.axis2</filter>
> </hidden-classes>
> If I understand well, by default the jar are always loaded from the parent
> classloader and not from the WEB-INF/lib directory of our web application
> (such as weblogic does for example). I find this quite dangerous because when
> I will migrate to Geronimo 2.0.2 which may contains new versions of jar, I
> will have to check that my application still work with those versions.
> The solution will be to hide (as above) all the jar of our web application
> and which are shipped with Geronimo. This may be quite forcing to do.
> Another solution may be to use the inverseClassloading flag of the 'Resource
> Adapter Geronimo Deployment Plan' if this is its purpose.
> What is the best practise?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
