[...]
You don't have to edit server.xml. In fact, you probably shouldn't if you can avoid it. You should be able to provide a context configuration file where you can put all the stuff you would normally put in server.xml for you webapp, but instead this is a standalone xml file which gets read kind of like how Apache server works with .htaccess files. You can even deploy your application with file in the META-INF directory of your .war file and it will get picked up by Tomcat (make sure to call it "context.xml" if you do this).
Hi Jake,
Do you mean that creating new services into Tomcat Server, creating new hosts into a service or creating new contexts into a host never needs the server.xml file to be edited?
Or should Tomcat Administration Tool save (persitently) changes somewhere else instead of server.xml file?
Anyhow, after shutting down and restarting Tomcat, all the changes done to Tomcat Server via Tomcat Administration Tool using "Commit Changes" are lost.
See:
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/host.html#Automatic%20Application%20Deployment
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/host.html#Automatic%20Application%20Deployment
Also see the manager app docs.
Yes, there is a large doc about Manager Application but the only detailed doc I found for admintool is from
<http://java.sun.com/webservices/docs/1.0/tutorial/doc/Admintool.html>
BTW, Tomcat5 is much better about all of this than Tomcat4.1 was. I recommend moving to Tomcat5 ASAP.
In first mail of this thread I mentioned it already is 5.0.16.
Jake
Thanks so much for your help
-- [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
