Hello Mark,
it is fixed at cvs and I am sure the this work with the next release
this days...
Regards,
Peter
Mark Thomas schrieb:
From: Remy Maucherat [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 27, 2004 11:26 PM
To: Tomcat Developers List
Subject: Re: WebappClassLoader: Lifecycle error
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 i
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 i
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 i
Hi,
>Options for fixing this are (I haven't look at the code for any of
these):
>- Do nothing and require the users to restart
>- Change the admin app to restart the context after changing the loader
>- Modify jasper to check the status of the classloader
>- Separate the creating and starting of
