关于java的英文文献+翻译8000字以上

东北石油大学本科生毕业设计（英文文献）

Overview of JSP Technology and JSP

application frameworks

1． 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

• 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

东北石油大学本科生毕业设计（英文文献）

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 would keep an eye on it, and if it

seemed to be catching on, they would follow his company's usual "embrace and extend"

strategy. At this point, Gosling lightheartedly interjected "You mean disgrace and

distend."

Now, the grievance that Gosling was airing was that he felt that this company would

the general idea, it even used many of the same special tags as ASP did..So, the question

becomes: why use JSP instead of one of these other technologies? Our first response is

that we are not arguing that everyone should. Several of those other technologies are

quite good and are reasonable options in some situations. In other situations, however,

JSP is clearly better. Here are a few of the reasons.

2.1 Versus .NET and Active Server Pages (ASP)

. NET is well-designed technology from Microsoft. ASP.NET is the part that directly

competes with servlets and JSP. The advantages of JSP are two fold.First, JSP is

portable to multiple operating systems and Web servers; you aren't locked into

deploying on Windows and IIS. Although the core .NET platform runs on a few non-

In addition, many developers still use the original version of ASP. With this version, JSP

东北石油大学本科生毕业设计（英文文献）

better suited to complex applications that require reusable components.

You could make the same argument when comparing JSP to the previous version of

ColdFusion; with JSP you can use Java for the "real code" and are not tied to a

particular server product. However, the current release of ColdFusion is within the

context of a J2EE server, allowing developers to easily mix ColdFusion and servlet/JSP

code.

2.2 Versus PHP

PHP (a recursive acronym for "PHP: Hypertext Preprocessor") is a free, open-source,

HTML-embedded scripting language that is somewhat similar to both ASP and JSP. One

advantage of JSP is that the dynamic part is written in Java, which already has an

scenes. But it is more convenient to write (and to modify!) regular HTML than to use a

zillion println statements to generate the HTML. Plus, by separating the presentation

from the content, you can put different people on different tasks: your Web page design

experts can build the HTML by using familiar tools and either leave places for your

servlet programmers to insert the dynamic content or invoke the dynamic content

indirectly by means of XML tags.

Does this mean that you can just learn JSP and forget about servlets? Absolutely not!

JSP developers need to know servlets for four reasons:

1. JSP pages get translated into servlets. You can't understand how JSP works without

understanding servlets.

东北石油大学本科生毕业设计（英文文献）

4. Some tasks are better accomplished by a combination of servlets and JSP than by

either servlets or JSP alone.

2.4 Versus JavaScript

JavaScript, which is completely distinct from the Java programming language, is

normally used to dynamically generate HTML on the client, building parts of the Web

page as the browser loads the document. This is a useful capability and does not

normally overlap with the capabilities of JSP (which runs only on the server). JSP pages

still include SCRIPT tags for JavaScript, just as normal HTML pages do. In fact, JSP

can even be used to dynamically generate the JavaScript that will be sent to the client.

So, JavaScript is not a competing technology; it is a complementary one.

It is also possible to use JavaScript on the server, most notably on Sun ONE

(formerly iPlanet), IIS, and BroadVision servers. However, Java is more powerful,

flexible, reliable, and portable.

2.5 Versus WebMacro or Velocity

like Apache Struts that augments JSP and servlet technology is a good idea when that

tool adds sufficient benefit to compensate for the additional complexity. But using a

nonstandard tool that tries to replace JSP is a bad idea. When choosing a technology,

you need to weigh many factors: standardization, portability, integration, industry

support, and technical features. The arguments for JSP alternatives have focused almost

exclusively on the technical features part. But portability, standardization, and

integration are also very important. For example, the servlet and JSP specifications

define a standard directory structure for Web applications and provide standard files

(.war files) for deploying Web applications. All JSP-compatible servers must support

these standards. Filters can be set up to apply to any number of servlets or JSP pages,

but not to nonstandard resources. The same goes for Web application security settings.

Besides, the tremendous industry support for JSP and servlet technology results in