JSP技术概述与应用框架外文翻译毕业设计

┊┊┊┊┊┊┊┊┊┊┊┊┊装┊┊┊┊┊订┊┊┊┊┊线┊┊┊┊┊┊┊┊┊┊┊┊┊附件1：外文原文Overview of JSP Technology and JSP application frameworks1．Benefits of JSPJSP 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.2.Advantages of JSP Over Competing TechnologiesA number of years ago,Marty was invited to attend a small20-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 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 take technology from other 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 product 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 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. and Active Server Pages(ASP).NET is well-designed technology from 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 platform runs on a few non-Windows platforms,the ASP part does not.You cannot expect to deploy serious applications on multiple servers and operating systems.For some applications,this difference does not matter.For others,it matters greatly.Second,for some applications the choice of the underlying language matters greatly.For example,'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 developers 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 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.2Versus PHPPHP(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 extensive API for networking,database access,distributed objects,and the like,whereas PHP requires learning an entirely new,less widely used language.A second advantage is that JSP is much more widely supported by tool and server vendors than is PHP.2.3Versus Pure ServletsJSP doesn't provide any capabilities that couldn't,in principle,be accomplished with servlets.In fact,JSP documents are automatically translated into servlets behind the 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.2.JSP consists of static HTML,special-purpose JSP tags,and Java code.What kind of Java code?Servlet code!You can't write that code if you don't understand servlet programming.3.Some tasks are better accomplished by servlets than by JSP.JSP is good at generating pages that consist of large sections of fairly well structured HTML or other character data.Servlets are better for generating binary data,building pages with highly variable structure,and performing tasks(such as redirection)that involve little or no output.4.Some tasks are better accomplished by a combination of servlets and JSP than by either servlets or JSP alone.2.4Versus 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.5Versus WebMacro or VelocityJSP is by no means perfect.Many people have pointed out features that could be improved.This is a good thing,and one of the advantages of JSP is that the specification is controlled by a community that draws from many different companies.So,the technology can incorporate improvements in successive releases.However,some groups have developed alternative Java-based technologies to try to address these deficiencies.This,in our judgment,is a ing a third-party tool 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 improvements that mitigate many of the criticisms of JSP.For example,the JSP Standard Tag Library and the JSP2.0expression language address two of the most well-founded criticisms:the lack of good iteration constructs and the difficulty of accessing dynamic results without using either explicit Java code or verbose jsp:useBean elements.┊┊┊┊┊┊┊┊┊┊┊┊┊装┊┊┊┊┊订┊┊┊┊┊线┊┊┊┊┊┊┊┊┊┊┊┊┊3.Misconceptions About JSPForgetting JSP Is Server-Side TechnologyHere are some typical questions Marty has received(most of them repeatedly).•Our server is running JDK1.4.So,how do I put a Swing component in a JSP page?•How do I put an image into a JSP page?I do not know the proper Java I/O commands to read image files.•Since Tomcat does not support JavaScript,how do I make images that are highlighted when the user moves the mouse over them?•Our clients use older browsers that do not understand JSP.What should we do?•When our clients use"View Source"in a browser,how can I prevent them from seeing the JSP tags?All of these questions are based upon the assumption that browsers know something about the server-side process.But they do not.Thus:•For putting applets with Swing components into Web pages,what matters is the browser's Java version—the server's version is irrelevant.If the browser supports the Java2platform, you use the normal APPLET(or Java plug-in)tag and would do so even if you were using non-Java technology on the server.•You do not need Java I/O to read image files;you just put the image in the directory for Web resources(i.e.,two levels up from WEB-INF/classes)and output a normal IMG tag.•You create images that change under the mouse by using client-side JavaScript, referenced with the SCRIPT tag;this does not change just because the server is using JSP.•Browsers do not"support"JSP at all—they merely see the output of the JSP page.So, make sure your JSP outputs HTML compatible with the browser,just as you would do with static HTML pages.•And,of course you need not do anything to prevent clients from seeing JSP tags;those tags are processed on the server and are not part of the output that is sent to the client. Confusing Translation Time with Request TimeA JSP page is converted into a servlet.The servlet is compiled,loaded into the server's memory,initialized,and executed.But which step happens when?To answer that question, remember two points:•The JSP page is translated into a servlet and compiled only the first time it is accessed after having been modified.•Loading into memory,initialization,and execution follow the normal rules for servlets.┊┊┊┊┊┊┊┊┊┊┊┊┊装┊┊┊┊┊订┊┊┊┊┊线┊┊┊┊┊┊┊┊┊┊┊┊┊The most frequently misunderstood entries are highlighted.When referring to the table,note that servlets resulting from JSP pages use the_jspService method(called for both GET and POST requests),not doGet or doPost.Also,for initialization,they use the jspInit method,not the init method.JSP page translated into servlet Servlet compiled Servlet loaded into server's memory jspInit called_jspService called.4.What are application frameworks:A framework is a reusable,semi-complete application that can be specialized to produce custom applications[Johnson].Like people,software applications are more alike than they are different.They run on the same computers,expect input from the same devices,output to the same displays,and save data to the same hard disks.Developers working on conventional desktop applications are accustomed to toolkits and development environments that leverage the sameness between applications.Application frameworks build on this common ground to provide developers with a reusable structure that can serve as the foundation for their own products.A framework provides developers with a set of backbone components that have the following characteristics:1.They are known to work well in other applications.2.They are ready to use with the next project.3.They can also be used by other teams in the organization.Frameworks are the classic build-versus-buy proposition.If you build it,you will understand it when you are done—but how long will it be before you can roll your own?If you buy it,you will have to climb the learning curve—and how long is that going to take?There is no right answer here,but most observers would agree that frameworks such as Struts provide a significant return on investment compared to starting from scratch,especially for larger projects.Other types of frameworks:The idea of a framework applies not only to applications but to application componentsas well. Throughout this article,we introduce other types of frameworks that you can use with Struts.These include the Lucene search engine,the Scaffold toolkit,the Struts validator,and the Tiles tag library. Like application frameworks,these tools provide semi-complete versions of a subsystem that can be specialized to provide a custom component.Some frameworks have been linked to a proprietary development environment.This is not the case with Struts or any of the other frameworks shown in this book.You can use any development environment with Struts:Visual Age for Java,JBuilder,Eclipse,Emacs,and Textpad are all popular choices among Struts developers.If you can use it with Java,you can use it with Struts.┊┊┊┊┊┊┊┊┊┊┊┊┊装┊┊┊┊┊订┊┊┊┊┊线┊┊┊┊┊┊┊┊┊┊┊┊┊Enabling technologies:Applications developed with Struts are based on a number of enabling technologies.These components are not specific to Struts and underlie every Java web application.A reason that developers use frameworks like Struts is to hide the nasty details behind acronyms like HTTP,CGI,and JSP.As a Struts developer,you don’t need to be an alphabet soup guru,but a working knowledge of these base technologies can help you devise creative solutions to tricky problems.Hypertext Transfer Protocol(HTTP):When mediating talks between nations,diplomats often follow a formal protocol.Diplomatic protocols are designed to avoid misunderstandings and to keep negotiations from breaking down.In a similar vein,when computers need to talk,they also follow a formal protocol.The protocol defines how data is transmitted and how to decode it once it arrives.Web applications use the Hypertext Transfer Protocol(HTTP)to move data between the browser running on your computer and the application running on the server.Many server applications communicate using protocols other than HTTP.Some of these maintain an ongoing connection between the computers.The application server knows exactly who is connected at all times and can tell when a connection is dropped.Because they know the state of each connection and the identity of each person using it,these are known as stateful protocols.By contrast,HTTP is known as a stateless protocol.An HTTP server will accept any request from any client and will always provide some type of response,even if the response is just to say no.Without the overhead of negotiating and retaining a connection,stateless protocols can handle a large volume of requests.This is one reason why the Internet has been able to scale to millions of computers.Another reason HTTP has become the universal standard is its simplicity.An HTTP request looks like an ordinary text document.This has made it easy for applications to make HTTP requests.You can even send an HTTP request by hand using a standard utility such as Telnet.When the HTTP response comes back,it is also in plain text that developers can read.The first line in the HTTP request contains the method,followed by the locationof the requested resource and the version of HTTP.Zero or more HTTP request headers follow the initial line.The HTTP headers provide additional information to the server.This can include the browser type and version, acceptable document types,and the browser’s cookies,just to name a few.Of the seven request methods, GET and POST are by far the most popular.Once the server has received and serviced the request,it will issue an HTTP response.The first line in the response is called the status line and carries the HTTP protocol version,a numeric status,and a brief description of the status.Following the status line,the server will return a set of HTTP response┊┊┊┊┊┊┊┊┊┊┊┊┊装┊┊┊┊┊订┊┊┊┊┊线┊┊┊┊┊┊┊┊┊┊┊┊┊headers that work in a way similar to the request headers.As we mentioned,HTTP does not preserve state information between requests.The server logs the request,sends the response,and goes blissfully on to the next request.While simple and efficient,a stateless protocol is problematic for dynamic applications that need to keep track of their users. (Ignorance is not always bliss.Cookies and URL rewriting are two common ways to keep track of users between requests.A cookie is a special packet of information on the user’s computer.URL rewriting stores a special reference in the page address that a Java server can use to track users.Neither approach is seamless,and using either means extra work when developing a web application.On its own,a standard HTTP web server does not traffic in dynamic content.It mainly uses the request to locate a file and then returns that file in the response.The file is typically formatted using Hypertext Markup Language(HTML)[W3C, HTML]that the web browser can format and display.The HTML page often includes hypertext links to other web pages and may display any number of other goodies,such as images and videos.The user clicks a link to make another request,and the process begins a new.Standard web servers handle static content and images quite well but need a helping hand to provide users with a customized,dynamic response.DEFINITION:Static content on the Web comes directly from text or data files,like HTML or JPEG files.These files might be changed from time to time,but they are not altered automatically when requested by a web browser.Dynamic content,on the other hand,is generated on the fly,typically in response to an individualized request from a browser.Common Gateway Interface(CGI):The first widely used standard for producing dynamic content was the Common Gateway Interface (CGI).CGI uses standard operating system features,such as environment variables and standard input and output,to create a bridge,or gateway,between the web server and other applications on the host machine.The other applications can look at the request sent to them by the web server and create a customized response.When a web server receives a request that’s intended for a CGI program,it runs that program and provides the program with information from the incoming request.The CGI program runs and sends its output back to the server.The web server then relays the response to the browser.CGI defines a set of conventions regarding what information it will pass as environment variables and how it expects standard input and output to be used.Like HTTP,CGI is flexible and easy to implement,and a great number of CGI-aware programs have been written.The main drawback to CGI is that it must run a new copy of the CGI-aware program for each┊┊┊┊┊┊┊┊┊┊┊┊┊装┊┊┊┊┊订┊┊┊┊┊线┊┊┊┊┊┊┊┊┊┊┊┊┊request.This is a relatively expensive process that can bog down high-volume sites where thousands of requests are serviced per minute.Another drawback is that CGI programs tend to be platform dependent.A CGI program written for one operating system may not run on another.5.Java servlets:Sun’s Java Servlet platform directly addresses the two main drawbacks of CGI programs.First, servlets offer better performance and utilization of resources than conventional CGI programs.Second, the write-once,run-anywhere nature of Java means that servlets are portable between operating systems that have a Java Virtual Machine(JVM).A servlet looks and feels like a miniature web server.It receives a request and renders a response. But,unlike conventional web servers,the servlet application programming interface(API)is specifically designed to help Java developers create dynamic applications.The servlet itself is simply a Java class that has been compiled into byte code,like any other Java object.The servlet has access to a rich API of HTTP-specific services,but it is still just another Java object running in an application and can leverage all your other Java assets.To give conventional web servers access to servlets,the servlets are plugged into containers.The servlet container is attached to the web server.Each servlet can declare what URL patterns it would like to handle.When a request matching a registered pattern arrives,the web server passes the request to the container,and the container invokes the servlet.But unlike CGI programs,a new servlet is not created for each request.Once the container instantiates the servlet,it will just create a new thread for each request.Java threads are much less expensive than the server processes used by CGI programs.Once the servlet has been created,using it for additional requests incurs very little overhead.Servlet developers can use the init()method to hold references to expensive resources,such as database connections or EJB Home Interfaces,so that they can be shared between requests.Acquiring resources like these can take several seconds—which is longer than many surfers are willing to wait.The other edge of the sword is that,since servlets are multithreaded,servlet developers must take special care to be sure their servlets are thread-safe.To learn more about servlet programming,we recommend Java Servlets by Example,by Alan R.Williamson[Williamson].The definitive source for Servlet information is the Java Servlet Specification[Sun,JST].6.JavaServer Pages:While Java servlets are a big step up from CGI programs,they are not a panacea.To generate the response,developers are still stuck with using println statements to render the HTML.Code that looks like:┊┊┊┊┊┊┊┊┊┊┊┊┊装┊┊┊┊┊订┊┊┊┊┊线┊┊┊┊┊┊┊┊┊┊┊┊┊out.println("<P>One line of HTML.</P>");out.println("<P>Another line of HTML.</P>");is all too common in servlets that generate the HTTP response.There are libraries that can help you generate HTML,but as applications grow more complex,Java developers end up being cast into the role of HTML page designers.Meanwhile,given the choice,most project managers prefer to divide development teams into specialized groups.They like HTML designers to be working on the presentation while Java engineers sweat the business ing servlets alone encourages mixing markup with business logic,making it difficult for team members to specialize.To solve this problem,Sun turned to the idea of using server pages to combine scripting and templating technologies into a single component.To build Java Server Pages,developers start by creating HTML pages in the same old way,using the same old HTML syntax.To bring dynamic content into the page,the developer can also place JSP scripting elements on the page.Scripting elements are tags that encapsulate logic that is recognized by the JSP.You can easily pick out scripting elements on JSP pages by looking for code that begins with<%and ends with%>.To be seen as a JSP page,the file just needs to be saved with an extension of.jsp.When a client requests the JSP page,the container translates the page into a source code file for a Java servlet and compiles the source into a Java class file—just as you would do if you were writing a servlet from scratch.At runtime,the container can also check the last modified date of the JSP file against the class file.If the JSP file has changed since it was last compiled,the container will retranslate and rebuild the page all over again.Project managers can now assign the presentation layer to HTML developers,who then pass on their work to Java developers to complete the business-logic portion.The important thing to remember is that a JSP page is really just a servlet.Anything you can do with a servlet,you can do with a JSP.7.JavaBeans:JavaBeans are Java classes which conform to a set of design patterns that make them easier to use with development tools and other components.DEFINITION A JavaBean is a reusable software component written in Java.To qualify as a JavaBean,the class must be concrete and public,and have a noargument constructor.JavaBeans expose internal fields as properties by providing public methods that follow a consistent design pattern. Knowing that the property names follow this pattern,other Java classes are able to use introspection to discover and manipulate JavaBean properties.The JavaBean design patterns provide access to the bean’s internal state through two flavors of┊┊┊┊┊┊┊┊┊┊┊┊┊装┊┊┊┊┊订┊┊┊┊┊线┊┊┊┊┊┊┊┊┊┊┊┊┊methods:accessors are used to read a JavaBean’s state;mutators are used to change a JavaBean’s state.Mutators are always prefixed with lowercase token set followed by the property name.The first character in the property name must be uppercase.The return value is always void—mutators only change property values;they do not retrieve them.The mutator for a simple property takes only one parameter in its signature,which can be of any type.Mutators are often nicknamed setters after their prefix.The mutator method signature for a weight property of the type Double would be: public void setWeight(Double weight)A similar design pattern is used to create the accessor method signature.Accessor methods are always prefixed with the lowercase token get,followed by the property name.The first character in the property name must be uppercase.The return value will match the method parameter in the corresponding mutator.Accessors for simple properties cannot accept parameters in their method signature.Not surprisingly,accessors are often called getters.The accessor method signature for our weight property is：public Double getWeight()If the accessor returns a logical value,there is a variant pattern.Instead of using the lowercase token get,a logical property can use the prefix is,followed by the property name.The first character in the property name must be uppercase.The return value will always be a logical value—either boolean or Boolean.Logical accessors cannot accept parameters in their method signature.The boolean accessor method signature for an on property would bepublic boolean isOn()The canonical method signatures play an important role when working with Java-Beans.Other components are able to use the Java Reflection API to discover a JavaBean’s properties by looking for methods prefixed by set,is,or get.If a component finds such a signature on a JavaBean,it knows that the method can be used to access or change the bean’s properties.Sun introduced JavaBeans to work with GUI components,but they are now used with every aspect of Java development,including web applications.When Sun engineers developed the JSP tag extension classes,they designed them to work with JavaBeans.The dynamic data for a page can be passed as a JavaBean,and the JSP tag can then use the bean’s properties to customize the output.For more on JavaBeans,we highly recommend The Awesome Power of JavaBeans,by Lawrence H. Rodrigues[Rodrigues].The definitive source for JavaBean information is the JavaBean Specification [Sun,JBS].Model2:The0.92release of the Servlet/JSP Specification described Model2as an architecture that uses。