thanks, but the whole point of this is to persist a property across restarts - whether 
they be the entire VM or just the web-app.

Is there a consistent wat to persist property information for the web-app to the 
filesystem, in the same way that sessions can be
persisted ?
I know that the servlet spec requires the ServletContext to provide a tempdir, so I 
will probably try serializing my properties to a
file in that dir.




> -----Original Message-----
> From: Jacob Kjome [mailto:[EMAIL PROTECTED]
> Sent: Friday, November 07, 2003 2:17 PM
> To: Tomcat Users List
> Subject: Re: How to persist web-app properties across restarts ?
>
>
>
> Put a singleton helper class in a parent classloader such as in shared or
> common Tomcat classloaders and manipulate collections there.  They will
> exist as long as the JVM (and Tomcat) is running.
>
> Otherwise, you should also be able to use stuff like System.setProperty().
>
> Jake
>
> At 01:51 PM 11/7/2003 -0500, you wrote:
>
> >I am looking for the most standard and lightweight way to persist some
> >properties about a web application across restarts of the web
> >application or the entire server.
> >Something like the ServletContext.setAttribute() method, but with the
> >persistence ability that you get from Http sessions would be
> >perfect.
> >I am using this for a management servlet that can indicate to load
> >balancing software that traffic needs to be directed away from a
> >given tomcat instance when it's in a certain state, and the management
> >servlet needs to remember what state it was last in when it's
> >application is restarted. Because it's used in monitoring I don't want any
> >dependancies on external data stores other than simple
> >file system.
> >
> >Thanks
> >
> >Steph
> >
> >
> >
> >
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: [EMAIL PROTECTED]
> >For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to