1. JSP can only be used very well in talents who are familiar with Java. And currently, Java programmers are still relatively small.
2. The JSP program is difficult to debug. The JSP page is first converted to a .java file (servlet) and then compile. such,
The error message actually points to the transformed .java file instead of JSP itself.
For example, an error in the first line of the .jsp file may be displayed as a 20th line. If you try to solve this problem by reverse tracking
Sometimes it will make the results funny. (However, in the RESIN engine, the error can be pointing to the error line of the .jsp file.)
You can also use some integrated design tools, such as VAJ or JDeveloper, but this is contrary to JSP easy to use this basic feature.
3. Database connections are not so easy. Most servlet engines do not support local buffer pool connections.
Therefore, there have been many code to complete this work.
4. It is difficult to select the appropriate servlet engine. There is no independent organization to provide independent Benchmark testing for various engines.
Provide business provides Benchmark testing for their own products, but the conclusion is usually given in the form of data.
However, the stability is avoided.
5. There are many problems in JSP programming, the author of Jason Hunter "Java Servlet Programming" writes one
Interesting articles compare JSPs and other alternative tools. Can participate http://www.servlets.com/soapbox/problems-jsp.html.
