JSP技术概述与应用框架外文翻译

《JSP技术概述与应用框架外文翻译》由会员分享，可在线阅读，更多相关《JSP技术概述与应用框架外文翻译（21页珍藏版）》请在毕设资料网上搜索。

1、 1 外文原文  Overview of JSP Technology and JSP application frameworks Autor: Zambon Giulio/ Sekler Michael Source: Springer-Verlag New York Inc 1  Benefits of JSP    JSP pages are translated into servlets. So, fundamentally, any task JSP pages can perform could also be accompli

2、shed 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 p

3、articular 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 &

4、nbsp; 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 wo

5、rk 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 con

6、tent.  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 ar

7、chitecture . You want the appropriate tool for the job, and servlets, by themselves, do not complete your toolkit. 2.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.

8、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

9、 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 大连交通大学 2012 届本科生毕业设计（论文）外文翻译  2 say that they would keep an eye on it, and if it seemed to be catching

10、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 take technology from ot

11、her companies and suborn it for their own purposes. But guess what? The shoe is on the other foot here. The Java community did not invent the idea of designing pages as a mixture of static HTML and dynamic code marked with special tags. For example, ColdFusion did it years earlier. Even ASP (a produ

12、ct from the very software company of the aforementioned manager) popularized this approach before JSP came along and decided to jump on the bandwagon. In fact, JSP not only adopted the general idea, it even used many of the same special tags as ASP did.So, the question becomes: why use JSP instead o

13、f 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  Versu

14、s .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 de

15、ploying on Windows and IIS. Although the core .NET platform runs on a few non-Windows platforms, the ASP part does not. You cannot expect to deploy serious ASP.NET applications on multiple servers and operating systems. For some applications, this difference does not matter. For others, it matters g

16、reatly.Second, for some applications the choice of the underlying language matters greatly. For example, although .NET's C# language is very well designed and is similar to Java, fewer programmers are familiar with either the core C# syntax or the many auxiliary libraries. In addition, many deve

17、lopers still use the original version of ASP. With this version, JSP has a clear advantage for the dynamic code. With JSP, the dynamic part is written in Java, not VBScript or another ASP-specific language, so JSP is more powerful and better suited to complex applications that require reusable compo

18、nents.    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