> From: Jeff Ramin [mailto:jeff.ra...@singlewire.com] > Subject: Re: possible to define/deploy a context but not start it? > > > Deploying a webapplication, though, always starts it. > > > > If a webapplication is included as a<Context> element in server.xml > > (usually not recommended), it is always deployed and started when > > server starts, regardless of deployOnStartup option. > > > > Besides the documentation, you may also want to look at the archives > > of this list. deployOnStartup/autoDeploy were discussed several > > times. > > > I want to start an application via JMX. Thus, tomcat needs to be > running, so that the JMX agent is available. But, I don't want my > web application to be available until it gets explicitly started > as the result of a JMX invocation of a WebModule bean.
Konstantin already gave you the answer: > > It is possible to turn off auto-deploy (autoDeploy, deployOnStartup), > > i.e. the webapplication will be present in webapps folder, but it will > > not be running, nor will it be listed by Tomcat Manager. > > > > Deploying a webapplication, though, always starts it. Your best bet is to leave the application _undeployed_ until you're ready for it, then deploy it. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
