Java Web Project Debugging __java

work will bring some interns or newcomers, most of the lack of experience, project debugging is their headache, the code out of the problem is often helpless, very affecting the efficiency. In fact, code debugging is a step to follow, the code out of the problem to do the first thing is to locate the problem, only know where the problem can be solved. A Java Web project is usually made up of a front-end and a backend, and the request is sent to the background code by the front end, so the first thing we need to do is determine whether the problem is in front or back, and make sure that the request parameters sent to the backend are right. Some students in the request parameter is not correct or the request does not arrive backstage the situation blindly to check the background code is wrong. foreground requests are usually submitted to the background via form, hyperlink, or Ajax, and we have to determine that the submitted link is right, then the parameters, and the submitted parameters can be obtained via the browser address or some browser debugging tools (such as Firefox's Firebug). If the request link is right and the parameters are right, that is the background problem, and the background problem is usually debugged through Eclipse debug, but in one case, the development uses some MVC frameworks, such as STRUTS2, spring MVC, etc. We have a breakpoint somewhere in the background, there is no response, there is a very simple way to add a breakpoint to the control layer of the code entrance, if not yet, that is the framework configuration problem, to check the configuration is correct.