From: Remy Maucherat [mailto:[EMAIL PROTECTED] > Sent: Tuesday, April 27, 2004 11:26 PM > To: Tomcat Developers List > Subject: Re: WebappClassLoader: Lifecycle error : CL stopped > > Shapira, Yoav wrote: > > Hi, > > > > I like #2: in fact, it seems like it should be strictly enforced for > > general stability and security, and I'm surprised the current code > > doesn't restart a context after changing its loader already. > > I think the admin webapp should stop the context before doing > anything > to its loader (and then start it again if it wants to).
What is the consensus on changing o.a.c.core.ContainerBase so any calls to setLoader(): 1 - stop the container if started 2 - change the loader 3 - starts the container if it was stopped in 1? It should reduce the possibility of lifecycle errors but I am not sure what the side-effects might be. Do we need to do a similar thing for setManager()? The back-up plan is to modify the admin app but this seems like the wrong place as all calls to setLoader() - both in the admin app and anywhere else - would need to be similarly wrapped with a stop and start. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
