that explains it!
I've been playing with the admin app for the past few days, adding users and roles, etc.
without realizing that it would effect the server.xml. I did expect it to overwrite the
tomcat-users.xml which it did, of course.
Btw, I had to recreate tomcat-users.xml again because after adding a new user thru
the admin interface, all the assigned roles where dropped from the existing users...
Neither did I find a way to assign a role to either existing or new user thru the interface.
In general, is admin application useful for anything?
In summary, saving changes in the admin application writes out a new server.xml
(with the line wrap destroyed), and it creates a backup of your original server.xml.
thank you, Jeff!
Ellen
At 06:07 PM 8/28/03 -0600, Jeff Tulley wrote:
I know that if you save out your changes in the admin application, it will write out server.xml and even add in things that weren't there previously (context definitions for items auto-deployed from the webapps directory, defaults settings I think, etc). I don't know if that is the culprit, because I'm not sure if it makes a backup copy like that. I know that when it does this, the line wrap is destroyed.
Do you have any 3rd party applications that would be messing with this file?
Jeff Tulley ([EMAIL PROTECTED]) (801)861-5322 Novell, Inc., The Leading Provider of Net Business Solutions http://www.novell.com
>>> [EMAIL PROTECTED] 8/28/03 5:30:16 PM >>> Has anybody any idea what triggers to generate a new server.xml file and replace the original?
It looks like my original server.xml file was mysteriously moved to server.xml.yyyy-mm-dd.hh-min-sec and was replaced with a new server.xml file, which although it kept the
configuration for all the original contexts, it looked unrecognizable. It seems completely generated because all of the comments are gone, including the ones which come with the default server.xml. Also, it is totally unreadable due to the line wrap.
This is the first time I've encountered something like this, and have never been aware of anything that could trigger generation of a new server.xml. On the day when this occurred, the was nothing unusual done to the server configuration on my part. The server was brought down on multiple occasions to pick up new contexts, that's all.
So, would anybody have any explanation for this?
thanks, Ellen
--------------------------------------------------------------------- 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]
