we are using virgo 3.5 for a server application and register several contexts via Web-ContextPath in the manifest. We configure the embedded tomcat server using the tomcat-server.xml configuration file. Is there any way to prevent the org.eclipse.gemini.web.tomcat.internal.Activator from immediately starting the tomcat server? We would like the tomcat server to initialise when the bundle starts but would like to start the server manually after all contexts have been deployed. This is to avoid the server replying with a 404 between the initialisation of the tomcat and the initialisation of the individual Web-ContextPath bundles. Is there any way to do this?
virgo-dev mailing listvirgo-dev@xxxxxxxxxxx