计算机毕业外文翻译---Struts——MVC 的一种开放源码实现

《计算机毕业外文翻译---Struts——MVC 的一种开放源码实现》由会员分享，可在线阅读，更多相关《计算机毕业外文翻译---Struts——MVC 的一种开放源码实现（15页珍藏版）》请在毕设资料网上搜索。

1、本科生毕业设计（论文）外文翻译   1 Struts an open-source MVC implementation By: Malcolm Davis.  Source: Struts-an open-source MVC implementationJ.IBM Systems Journal This article introduces Struts, a Model-View-Controller implementation that uses servlets and JavaServer Pages (JSP) technology. Struts can

2、 help you control change in your Web project and promote specialization. Even if you never implement a system with Struts, you may get some ideas for your future servlets and JSP page implementation. Introduction Kids in grade school put HTML pages on the Internet. However, there is a monumental dif

3、ference between a grade school page and a professionally developed Web site. The page designer (or HTML developer) must understand colors, the customer, product flow, page layout, browser compatibility, image creation, JavaScript, and more. Putting a great looking site together takes a lot of work,

4、and most Java developers are more interested in creating a great looking object interface than a user interface. Java Server Pages (JSP) technology provides the glue between the page designer and the Java developer.  If you have worked on a large-scale Web application, you understand the term c

5、hange. Model-View-Controller (MVC) is a design pattern put together to help control change. MVC decouples interface from business logic and data. Struts is an MVC implementation that uses Servlets 2.2 and JSP 1.1 tags, from the J2EE specifications, as part of the implementation. You may never implem

6、ent a system with Struts, but looking at Struts may give you some ideas on your future Servlets and JSP implementations. Model-View-Controller (MVC) JSP tags solved only part of our problem. We still have issues with validation, flow control, and updating the state of the application. This is where

7、MVC comes to the rescue. MVC helps resolve some of the issues with the single module approach by dividing the problem into three categories:   Model The model contains the core of the application's functionality. The model encapsulates the state of the application. Sometimes the only functi

8、onality it contains is state. It knows nothing about the view or controller.   View The view provides the presentation of the model. It is the look of the application. The view can access the model getters, but it has no knowledge of the setters. In addition, it knows 本科生毕业设计（论文）外文翻译   2 n

9、othing about the controller. The view should be notified when changes to the model occur. Controller The controller reacts to the user input. It creates and sets the model.  MVC Model 2 The Web brought some unique challenges to software developers, most notably the stateless connection between

10、the client and the server. This stateless behavior made it difficult for the model to notify the view of changes. On the Web, the browser has to re-query the server to discover modification to the state of the application. Another noticeable change is that the view uses different technology for impl

11、ementation than the model or controller. Of course, we could use Java (or PERL, C/C+ or what ever) code to generate HTML. There are several disadvantages to that approach:   Java programmers should develop services, not HTML.   Changes to layout would require changes to code.   Custom

12、ers of the service should be able to create pages to meet their specific needs.   The page designer isn't able to have direct involvement in page development.   HTML embedded into code is ugly.  For the Web, the classical form of MVC needed to change. Figure 4 displays the Web ada

13、ptation of MVC, also commonly known as MVC Model 2 or MVC 2.  Figure 4. MVC Model 2 Struts, an MVC 2 implementation Struts is a set of cooperating classes, servlets, and JSP tags that make up a reusable MVC 2 design. This definition implies that Struts is a framework, rather than a library, but

14、 Struts also contains an extensive tag library and utility classes that work independently of the framework. Figure 5 displays an overview of Struts.  Figure 5. Struts overview 本科生毕业设计（论文）外文翻译   3 Struts overview Client browser An HTTP request from the client browser creates an event. The

15、Web container will respond with an HTTP response.   Controller The Controller receives the request from the browser, and makes the decision where to send the request. With Struts, the Controller is a command design pattern implemented as a servlet. The struts-config.xml file configures the Cont

16、roller.   Business logic The business logic updates the state of the model and helps control the flow of the application. With Struts this is done with an Action class as a thin wrapper to the actual business logic.   Model state The model represents the state of the application. The busin

17、ess objects update the application state. ActionForm bean represents the Model state at a session or request level, and not at a persistent level. The JSP file reads information from the ActionForm bean using JSP tags.   View The view is simply a JSP file. There is no flow logic, no business lo

18、gic, and no model information - just tags. Tags are one of the things that make Struts unique compared to other frameworks like Velocity.  Struts details Displayed in Figure 6 is a stripped-down UML diagram of the org.apache.struts.action package. Figure 6 shows the minimal relationships among ActionServlet (Controller), ActionForm (Form State), and Action (Model Wrapper).  Figure 6. UML diagram of the relationship of the Command (ActionServlet) to the Model (Action & ActionForm)