Hi David,
Either 1 or 2 above allows you to stop, unload, make alterations, whatever to a specific webapp without having to bounce the tomcat server and disrupting any/all the other webapps running on that tomcat instance. Just go into the manager webapp, stop the webapp, make any alterations you need -- update jars, etc., ... and then start the webapp again in the manager webapp.
This has inevitably lead to out of memory exceptions when restarting an apps and taking the whole server down. Not fun. Which version of Tomcat are you using? Have you been able to restart Magnolia instances this way, with other apps running (say, *for example*, jira and confluence? :D)
cheers, -g ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/docs/en/editor/stayupdated.html ----------------------------------------------------------------
