Ad 1) there is the problem the service should be accessible all the time 24/7/365 (liveline of a company) and we need to change the structure during runtime.

Ad 2) a persisten manager is in use, but not for short living data.

Thanx Mike

-----Ursprüngliche Nachricht-----
Von: Tim Funk [mailto:funkman@(protected)]
Gesendet: Dienstag, 19. August 2003 14:04
An: Tomcat Users List
Betreff: Re: about web.xml and servlet mapping and reloading

1) Stop and start the context. Reload only dumps the classloader and creates
a new one.
2) Use a persistent manager (JBDC, file, ...) which will probably still be
required with a context stop/start

-Tim

Nitschke Michael wrote:
> I try to dynamically create and change servlet mapping in the web.xml in
> full production mode and then reload/reread the web.xml to update the
> mapping, but as i read in the manage application:
>
> <quote>NOTE: The /WEB-INF/web.xml web application configuration file is
> not reread on a reload. If you have made changes to your web.xml file
> you must stop then start the web application. </quote>
>
> it does not work like i need it, because the tomcat should not be
> restarted (loss of temporary data).
>
> Is there a way to keep the mappings available for tomcat and reloadable
> (no tomcat restart requiered).
>
>
>
> Thanx Mike
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
For additional commands, e-mail: tomcat-user-help@(protected)


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
For additional commands, e-mail: tomcat-user-help@(protected)