Eclipse 3 + Lomboz 3 + Tomcat 5 (4) Revision and Supplement

Today is Thanksgiving, I finally have time to read it all over again, I really can't think of it. One of my little articles have got up so much response and support. These will become my motivation, thank you first.

Here are some of the main issues:

Tomcat version issues, this earliest appearance, basically because Tomcat's start-up mode (path settings) has changed after 5.0.27, Lomboz 3 does not adapt to this later version. There are two solutions:

Do not use the version 5.0.25 when developed, but you can use a new version when you actually deploy the application, such as 5.0.27, 28, etc. Modify a profile in Lomboz (specifically under the Eclipse directory, plugins / com.ObjectLearn.jdt.j2ee_3.0.1 / serve / tomcat5-x.server), this method allows Tomcat to start normally, but in later debugging There may be other problems, this is not guaranteed. I personally recommend everyone to use the first method, relatively simple, and almost certainly feasible. Because there are too many friends who are caught by this problem, I have never started the problem with one way. In fact, this issue should not be, purely my personal mistakes. From the common sense, the XML node name is case sensitive. I was very annoyed by the editor in this blog, and the configuration of this common sense was configured. It is sorry that many friends have plagued a lot of time on this issue. As many friends point out, in the correct configuration file, the node name, the attribute name is unfair, thank you all those who point out this question. The correct configuration file is as follows: The specific directory must be modified according to the actual situation, but the node name, the attribute name must not be wrong. When you copy, you have to go to the space before and after the "<" and end ">" symbol (here, it is because the typography problem) needs to manually change _jsp.java to capture the problem, I am answering a friend. After this problem, you will be repeated again. Manually change the method of making breakpoints is not a positive solution. If your development environment must change the interception point, it is because your settings have problems, I have never changed any _jsp.java file, which can be debugged. If you come back, if you must change it, you can debug it, then it will be changed. This is not a big thing, debugging is a big problem. Just hope that everyone knows this is not the right way.

Then, the article about Eclipse, Lomboz and Tomcat series is whose origin, transaction, or reference, please indicate.