tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carreira, Jason" <>
Subject RE: request for review: server/config discussion
Date Tue, 20 Jul 1999 21:43:17 GMT
> -----Original Message-----
> From: Craig R. McClanahan []
> There's (at least) one more need to be considered with 
> respect to dynamic
> configurations, and it doesn't fit very neatly into an roles 
> model -- at least
> not in my head.  And that is the idea of asking the currently 
> running server to
> "persistify" (blame James, I am not making this word up :-) 
> the configurations
> data that will reproduce the current environment as 
> faithfully as possible.
> Otherwise, if you make a dynamic change to the running 
> server, but forget to
> make the same change in the config files, you are going to 
> lose that change the
> next time you really do restart the server.
> Doing this would probably be easier if the configurations 
> data was itself an
> object (like a DOM tree or something) that coulld be asked 
> generically to "write
> yourself to this output stream", rather than making every 
> server component for
> reconstructing configurations settings from the currently set 
> properties or
> whatever.

Absolutely... the config should be an object in memory that manages its own
persistence. It should be a listener for itself, receiving change
notifications and persisting its modified state to whatever persistent store
is specified, or even to multiple stores, such as a DB, XML file, JNDI,

View raw message