When Myeclipse-web is developed, when you restart Tomcat, redeploy

When Myeclipse-web is developed, when you restart Tomcat, redeploy

Conclusion Although not all, but know is still earlier, but know last night suddenly flashed again (ghost know why), so decided to write to blog. Quite a year, very painful, silly every time to restart Tomcat, or redeploy, that is called two AH (more important is slow).

1. Redeployment

Niang, this situation this year has not seen, I use is MyEclipse 6.6, but the past met to more, unexplained. This is even less so now that the MyEclipse has been upgraded. In short, now this is a small probability event, it is not possible to redeploy it.

To add, there's just one situation that needs to be redeployed: it was when I added the jar package through the user library because the jar package didn't replicate in the past.

2. Restart Tomcat

According to my practice and theory, practice comes from every day to write the program, the theory comes from the "Java Virtual Machine Second Edition", there is time to see, a little enlightened feeling, but now I do not remember the place, looking back to find the principle [more].

Add a new class, modify a class name, add a method, modify a method name, add or remove parameters for a method (Niang, and forget the jargon [quest-], is the method test (string str) into test () or test (string str, int i)), and adding or removing exceptions for the method, that is, test () to test () throws exception all need to restart Tomcat.

3. No need to do anything

Modify JSP, HTML, JS and other things, remember the browser to empty the cache ah.

4. Other

Some things are based on configuration to determine whether to restart, such as struts2 (see Struts2 profile).

When Myeclipse-web is developed, when you restart Tomcat, redeploy