【正文】 東華理工大學(xué)畢業(yè)設(shè)計(jì) 外文翻譯 1 JSP Technology（ 外文原文 ） JSP (JavaServer Pages) is a kind of based on Java script technology. In many of the advantages of JSP, one of which is it can the HTML code from Web pages in the business logic of the effectively separated. With JSP visit reusable ponents, such as Servlet, JavaBean and based on Java Web applications. JSP also support in Web page direct embedded Java code. The two methods can visit JSP files: browser to send files request, sent to the JSP Servlet request. JavaServer Pages technology is an extension of the Java Servlet technology. Servlets are platformindependent, serverside modules that fit seamlessly into a Web server framework and can be used to extend the capabilities of a Web server with minimal overhead, maintenance, and support. Unlike other scripting languages, servlets involve no platformspecific consideration or modifications。 they are application ponents that are downloaded, on demand, to the part of the system that needs them. Together, JSP technology and servlets provide an attractive alternative to other types of dynamic Web scripting/programming by offering: platform independence。 enhanced performance。 separation of logic from display。 ease of administration。 extensibility into the enterprise。 and, most importantly, ease of use. The Unified Expression Language (EL) The simple EL included in JSP technology offers many advantages to the page author. Using simple expressions, page authors can easily access external data objects from their pages. The JSP technology container evaluates and resolves these expressions as it encounters them. It then immediately returns a response because the JSP requestprocessing model has only one phase, the render phase. However, because the requestprocessing model does not support a postback, all JSP expressions are readonly. Unlike JSP technology, JavaServer Faces technology supports a multiphase life cycle. When a user enters values into the JavaServer Faces UI ponents and submits the page, those values are converted, validated, and propagated to serverside data objects, after which ponent events are processed. In order to perform all these tasks in an orderly fashion, the JavaServer Faces life cycle is split into separate phases. Therefore, JavaServer Faces technology evaluates expressions at different phases of the life cycle rather than immediately, as JSP technology would do. 東華理工大學(xué)畢業(yè)設(shè)計(jì) 外文翻譯 2 JSP technology friend or foe? Presentation technology was designed to transform plain ol39。 raw Web content into content wrapped in an attractive presentation layer. JavaServer Pages (JSP) technology, Sun39。s presentation model and part of the J2EE platform, has received significant attention. There are both advantages and disadvantages to using JSP technology, and Web developers should be aware of the good and the bad and know that they don39。t have to be limited to this single technology. In fact, these days a number of presentation technologies are available. This article begins by defining the problems presentation technologies were designed to solve. It then examines the specific strengths and weaknesses of the JSP model. Finally, it introduces some viable alternatives to Sun39。s presentation technology. A bit of historyBefore diving into an explanation of presentation technology, it39。s helpful to fill in some details on the situation that led to the birth of the technology. Just 10 short years ago, the term thin client was a novelty. We still lived in a world of desktop applications, powered by wimpy 286 microprocessors with 14inch monitors that we squinted at. Boy, have times changed! Now my desktop does nothing but power a Web browser, while servers from Sun, IBM, HP, Compaq, and the rest churn out putations, business logic, and content. And that little monitor? Replaced by flatscreen, plasma, whopping 21 and 25inch beauties. Why? So we can see the intricate and plex HTML displays that serve as a frontend to these powerful applications. No longer does a clunky interface suffice。 now we expect flashy graphics, moving images, colorcoordinated presentations that would look good in any room in the house, and speedy rendering to boot. The premiseToday, a decade beyond those fledgling Windows applications, we are still dealing with this huge shift in the presentation paradigm. The woeful Visual Basic and C programmers who remain now find themselves working either on backend systems or Windowsonly applications, or they have added a Webcapable language such as the Java language to their toolbox. An application that doesn39。t support at least three of four MLisms such as HTML, XML, and WML is considered shabby, if not an outright failure. And, of course, that means we all care very deeply about the ability to easily develop a Web presentation it turns out, using the new Inter, and all the languages we have at our disposal Java, C, Perl, Pascal, and Ada, among others hasn39。t been as easy as we might have hoped. A number of issues creep up when it es to taking the programming languages everyone used for backend systems and leveraging them to generate markup 東華理工大學(xué)畢業(yè)設(shè)計(jì) 外文翻譯 3 language suitable for a client. With the arrival of more options on the browser (DHTML and JavaScript coding, for example), the increase in graphic artist talent in the Web domain, and tools that could create plex interfaces using standard HTML, the demand for fancy user interfaces has grown faster than our ability to develop these front ends to our applications. And this has given rise to presentation technol