[ http://issues.apache.org/jira/browse/GERONIMO-2237?page=comments#action_12423911 ] Jeff Genender commented on GERONIMO-2237: -----------------------------------------
"Best of all would be to get Spring out of the parent hierarchy of web apps so this problem just went away." Its out...it was out since 1.1 release. The patch has no effect since Spring was removed from the server in 1.1. The filter is not even in Jetty AFAICT. This is a bigger bug than having to place the filters in the DDs (which isn't necessary). I move that we apply the patch and fix the classloaders for 1.2, which is the real problem IMHO. > Filtering of springframework.org in TomcatDeployer plan creates CNF > Exceptions in Ears > -------------------------------------------------------------------------------------- > > Key: GERONIMO-2237 > URL: http://issues.apache.org/jira/browse/GERONIMO-2237 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Tomcat > Affects Versions: 1.1 > Reporter: Jeff Genender > Priority: Blocker > Fix For: 1.1.1 > > > Filtering of springframework.org in TomcatDeployer plan creates ClassNotFound > Exceptions in Ears when it tries to use a component that uses Spring in the > EAR. We originally filtered this to automatically prevent Spring clashing > with a server based Spring (from 1.0). This was fine for wars but when used > iun an ear, the web container is blocked from using the EAR version. I > recommend we remove these filters as SPrin is not usable in an EAR. > Recommended patch for configs/tomcat-deployer: > Index: src/plan/plan.xml > =================================================================== > --- src/plan/plan.xml (revision 426203) > +++ src/plan/plan.xml (working copy) > @@ -46,10 +46,7 @@ > <type>car</type> > </dependency> > </dependencies> > - <hidden-classes> > - <filter>antlr.</filter> > - <filter>org.springframework.</filter> > - </hidden-classes> > + <hidden-classes/> > <non-overridable-classes> > <filter>java.</filter> > <filter>javax.</filter> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
