My question is deploying to an instance of a Tomcat server that hosts multiple applications and application host contexts for Struts, Spring, and Hibernate. I would like to deploy the changes to a single application without rebooting my Tomcat server.
As an example, in many cases in our company we must deploy new applications or versions of applications in our tomcat environment, and the process can be:
- Move the class and jsp to the exploded folder, then reload the context or
- Another scenario is to deploy new features that require changes in xml contexts, such as
struts-config.xml or spring-application-context.xml .
Currently, we need to restart the web server to load the new configuration. This would be normal if Tomcat did not have other live applications that we did not want to interrupt and restart. As an example, if I have an application that uses hibernate and struts, then I need to redeploy it to the Tomcat server with many other applications running, and I deploy the new application and restart the server. This is not perfect.
So the question is, when do I need to reload when deploying changes to Tomcat, including changes in context? Is there a way to make a hot deployment just for this particular application and possibly re-launch its context without restarting the web server?
Thank you so much! Regards
spring tomcat deployment struts
joksy82 Oct 25 2018-11-11T00: 00Z
source share