外文原文
Overview of JSP Technology
Benefits of JSP
JSP pages are translated into servlets. So, fundamentally, any task JSP pages can perform could also be
accomplished by servlets. However, this underlying equivalence does not mean that servlets and JSP pages
are equally appropriate in all scenarios. The issue is not the power of the technology, it is the convenience,
productivity, and maintainability of one or the other. After all, anything you can do on a particular computer
platform in the Java programming language you could also do in assembly language. But it still matters
which you choose.
JSP provides the following benefits over servlets alone:
• It is easier to write and maintain the HTML. Your static code is ordinary HTML: no extra backslashes, no
double quotes, and no lurking Java syntax.
• You can use standard Web-site development tools. Even HTML tools that know nothing about JSP can be
used because they simply ignore the JSP tags.
• You can divide up your development team. The Java programmers can work on the dynamic code. The
Web developers can concentrate on the presentation layer. On large projects, this division is very important.
Depending on the size of your team and the complexity of your project, you can enforce a weaker or stronger
separation between the static HTML and the dynamic content.
Now, this discussion is not to say that you should stop using servlets and use only JSP instead. By no means.
Almost all projects will use both. For some requests in your project, you will use servlets. For others, you
will use JSP. For still others, you will combine them with the MVC architecture . You want the appropriate
tool for the job, and servlets, by themselves, do not complete your toolkit.
Advantages of JSP Over Competing Technologies
A number of years ago, Marty was invited to attend a small 20-person industry roundtable discussion on
software technology. Sitting in the seat next to Marty was James Gosling, inventor of the Java programming
language. Sitting several seats away was a high-level manager from a very large software company in
Redmond, Washington. During the discussion, the moderator brought up the subject of Jini, which at that
time was a new Java technology. The moderator asked the manager what he thought of it, and the manager
responded that it was too early to tell, but that it seemed to be an excellent idea. He went on to say that they
