On 6/9/2010 9:36 AM, Thomas Kloeber wrote:
André Warnier wrote on 09.06.2010 15:20:
Inthink you should have a look at the Manager application (delivered
along with Tomcat when downloading from the main Tomcat site).
The Manager allows you to deploy, undelploy, start and stop one
application, without stopping/restarting Tomcat as a whole.
Since it is open-source, you can have a look at how it does that, and
do the same. Or just look at how the form works, and call the Manager
the same way.
that's exactly what I did already, but I couldn't find/understand
what/where/how it does it.
Is this such an unusal thing that one has to configure webapp files with
site specific information?
Beyond 1-time initial configuration, I would say it is unusual.
How do people do it?
In my case, the site-specific settings are either in the backing
database or in a separate properties file, and all can be configured
from within the application itself (using a separate administrative
login, of course). As part of the method that saves the settings to
permanent storage, I also apply them to the application's current
settings so they take effect immediately.
D
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
