-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 David,
David Kerber wrote: > Is there a built-in method of having different settings for each > instance of tomcat, but which won't require bouncing tomcat to put the > changes into effect? I know I could roll my own with a disk file (like > a windows .ini file), but would rather not have to do that if I can > avoid it. You could store your preferences in a JNDI context. If you use <env-entry> in your web.xml instead of using <context-param> or something else, then they will be automatically loaded into the directory on startup, so you get your default values. You should be able to use an off-the-shelf JNDI browser to navigate your preferences and perhaps even change them. You can always write your own code to change them, of course. (There's a parallel thread on the list right now about the immutability of JNDI information, so you might want to pay attention to what's going on, there). I've never done this myself but it sounds feasible. Another option would be to just use a properties file on the disk and monitor it for changes, similar to how TC's reloadable contexts monitor files. It's kinda messy, but it'll work. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFuL0d9CaO5/Lv0PARAiuyAJ4ya3m0r9AEbxNZ0BQhA8TZkrGVMACgjkuR NzLMzOE3ElBYP2tt4ChHTOI= =ji7Y -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
