Implementing JVM Hot Deployment with Jrebel, modifying classes without restarting Tomcat

One of the problems we often encounter with eclipse development is the need to restart Tomcat after modifying the class file to take effect, even if you use some Tomcat plug-ins, sometimes modifying the method name or adding a class, which also requires a reboot. With the Jolt Jackpot Jrebel, you can easily implement a JVM hot deployment, no matter how you modify the class without restarting Tomcat

First, download Jrebel, go to http://fly-hyp.javaeye.com/blog/350498, and then configure Eclipse

Add-noverify-javaagent:d:/youpath/jrebel.jar to the startup parameter here you need to change the path to your native, and sometimes you need to put Javarebel.jar in the project's Jar directory

You can then turn off the automatic restart of the server settings so that every time you modify the file, Eclipse will restart the service for you.

Implementing JVM Hot Deployment with Jrebel, modifying classes without restarting Tomcat