Spring的webMVC构架模式(转)

web Mvc with the spring framework
Spring的web MVC 构架模式

Juergen Hoeller

1. Introduction: Spring the Application Framework
1.介绍&＃xff1a;Spring 应用构架

When first confronted with the Spring Framework, one might be tempted to think: "Oh no, not yet another web framework". This article will outline why Spring isn&＃39;t particularly a web framework but a generic lightweight application framework with dedicated web support, and show the architectural differences to struts and WebWork

当你第一次看到Spring的时候&＃xff0c;你一定会说:"哦 不&＃xff0c;又一种web 构架".这篇文章将告诉你Spring明显区别于其他轻量级application framework,
它将专注于web的支持&＃xff0c;与struts 和 webwork有着明显的区别。

In contrast to Struts or WebWork, Spring is an application framework for all layers: It offers a bean configuration foundation, AOP support, a JdbC abstraction framework, abstract transaction support, etc. It is a very non-intrusive effort: Your application classes do not need to depend on any Spring classes if not necessary, and you can reuse every part on its own if you like to. From its very design, the framework encourages clean separation of tiers, most importantly web tier and business logic: e.g. the validation framework does not depend on web controllers. Major goals are reusability and testability: Unnecessary container or framework dependencies can be considered avoidable evils.

在和struts 和 webwork的对比上,Spring是一个服务于所有层面的application framework:提供了bean的配置基础&＃xff0c;AOP的支持&＃xff0c;JDBC的提取框架&＃xff0c;
抽象事务支持&＃xff0c;等等。它有一个非常显著的特点&＃xff1a;在某个层面上如果你不需要Spring的支持&＃xff0c;你就可以不使用String的class&＃xff0c;只使用它的某一部分的功能。
从它的设计理念&＃xff0c;你可以看到String 帮助你实现了真正的逻辑层和web层的分离&＃xff1a;例如。一个校验应用将不用依靠controllers&＃xff0c;就可以实现。这样的目标是
更好的重用和易测&＃xff1a;过分依靠不必要的容器和框架将不能实现这一点。

Of course, Spring&＃39;s own web support is nicely integrated with the framework&＃39;s general patterns. Nevertheless, replacing the web solution with Struts, WebWork, or the like is easy. Both with Spring&＃39;s web support or a different one, Spring allows for building a true dedicated middle tier in the web container, with the option to reuse exactly the same business logic in test environments or standalone applications. And within J2EE, your business logic will not unnecessarily depend on container services like JTA or EJB - allowing complex, well-architected web applications to run in a "simple" container like tomcat or Resin.

当然,Spring 的自己的web支持和通常框架模式的细致完整.然而&＃xff0c;Spring替换struts,webwork或者其他的web方案非常的容易.对于Spring的web支持或者不同的地方&＃xff0c;Spring 允许你在web容器里面建立一个中间层&＃xff0c;在测试环境或者标准独立的应用里面来设置重用你的商务逻辑.还有在J2EE环境里面&＃xff0c;你的商务逻辑不必依靠容器提供的服务&＃xff0c;像JTA ,EJB的支持.良好的构架的web应用可以运行在任何容器上&＃xff0c;如&＃xff0c;Tomcat 或者 Resin.

Note that Spring doesn&＃39;t generally aim to compete with existing solutions. It rather fosters seamless integration with standards like servlet, JSP, JTA, JNDI, JDBC, and JDO, and well-suited tools like hibernate, Velocity, Log4J, and Caucho&＃39;s Hessian/Burlap. The framework is designed to grow with the needs of your applications, in terms of technology choice: For example, you will probably use JTA via Spring&＃39;s JtaTransactionManager if you need distributed transactions - but only then, as there are perfect replacements for single databases, like DatasourceTransactionManager or HibernateTransactionManager.

值得注意的是&＃xff0c;Spring 不是和已经存在的解决方案进行竞争. 我们鼓励结合标准的技术&＃xff0c;如&＃xff0c; Servlet, JSP, JTA, JNDI, JDBC, and JDO, 和非常匹配的工具&＃xff0c;如&＃xff0c;Hibernate, Velocity, Log4J, and Caucho&＃39;s Hessian/Burlap.这个框架的的设计思想是在你的应用需要改良的时候&＃xff0c;你将会做一些技术的选择:例如,如果你需要分布式事务处理&＃xff0c;你可能需要用Spring的Jta TransactionManager 来实现JTA服务.或者&＃xff0c;用DataSourceTransactionManager or HibernateTransactionManager 来实现美妙完美的单个数据库交换。

2. Web MVC: The Design of Spring&＃39;s Web Framework
Web MVC:Spring web 框架的设计思想

Spring&＃39;s web framework is designed around a DispatcherServlet that dispatches requests to handlers, with configurable handler mappings, view resolution, and locale and theme resolution. The default handler is a very simple Controller interface, just offering a "ModelAndView handleRequest(request,response)" method. This can already be used for application controllers, but you will prefer the included implementation hierarchy, consisting of AbstractController, AbstractCommandController, MultiActionController, SimpleFormController, AbstractWizardFormController. Application controllers will typically be subclasses of those. Note that you can choose an appropriate base class: If you don&＃39;t have a form, you don&＃39;t need a FormController. This is a major difference to Struts.

Spring 框架通过配置操作mappings,展示resolution,本地化和模版集成围绕着分派请求操作的servlet - DispatcherServlet设计的.缺省的操作是一个非常简单的控制接口,
他只提供了ModelAndView handleRequest(request,response)方法.这将用于一个应用的控制,但是,如果你想包含多个层次的控制&＃xff0c;AbstractController, AbstractCommandController, MultiActionController, SimpleFormController, AbstractWizardFormController 将帮助你完成.应用控制将代表那些子系统.注意&＃xff0c;你可以选择一个适当的基类:如果你没有 web form,你就不必用FormController.这就是和Struts最大的不同.

You can take any object as command or foRM object: There&＃39;s no need to implement an interface or derive from a base class. Spring&＃39;s data binding is highly flexible, e.g. it treats type mismatches as validation errors that can be evaluated by the application, not as system errors. So you don&＃39;t need to duplicate your business objects&＃39; properties as Strings in your form objects, just to be able to handle invalid submissions, or to convert the Strings properly. Instead, it&＃39;s often preferable to bind directly to your business objects. This is another major difference to Struts which is built around required base classes like Action and ActionForm - for every type of action.

你可以通过命令或者form对象来操作任何对象:这不需要接口工具或者一个基础类的驱动.Spring的数据邦定是非常的灵活的.举例来说,它描述了具有在应用范围内的校验错误的输入机制,但不是系统错误.所以在你的form对象里面你不必复制你的业务对象的string属性,只操作出错的子任务,或者适当地转换string.换句话说,它通常可以很好的直接邦定你的业务对象.
这也是和struts围绕请求基础类Action 和 ActionForm (每个action操作类型) 建立主要的不同之一.

Compared to WebWork, Spring has more differentiated object roles: It supports the notion of a Controller, an optional command or form object, and a model that gets passed to the view. The model will normally include the command or form object but also arbitrary reference data. Instead, a WebWork Action combines all those roles into one single object. WebWork does allow you to use existing business objects as part of your form, but just by making them bean properties of the respective Action class. Finally, the same Action instance that handles the request gets used for evaluation and form population in the view. Thus, reference data needs to be modelled as bean properties of the Action too. These are arguably too many roles in one object.

对比WebWork,Sping更多的区别在于对象角色:Sping支持控制器的感念,一个操作命令或者form对象,和得到数据传递给视图的模式.这个模式通常包含命令和form对象,但有时也包含任意的参考数据.换句话说,一个WebWork Action联合所有这些角色到一个单独的对象.WebWork 允许你用已经存在的业务对象作为你 form 的一部分,但是只生成各自Action 的 bean 属性. 最后,操作请求的Action 实例在一个视图里面获得付值和form population. 然而,参考数据也需要作为Action 的属性被模拟. 一个类里面有太多的角色是值得讨论的.

Regarding views: Spring&＃39;s view resolution is extremely flexible. A Controller implementation can even write a view directly to the response, returning null as ModelAndView. In the normal case, a ModelAndView instance consists of a view name and a model Map, containing bean names and corresponding objects (like a command or form, reference data, etc). View name resolution is highly configurable, either via bean names, via a properties file, or via your own ViewResolver implementation. The abstract model Map allows for complete abstraction of the view technology, without any haSSLe: Be it JSP, Velocity, or anything else - every renderer can be integrated directly. The model Map simply gets transformed into an appropriate format, like JSP request attributes or a Velocity template model.

关于视图:Spring的视图方案非常的灵活. 一个控制器执行可以通过response 返回ModelAndView对象null,就可以直接写到一个视图.在通常的状况下,一个ModelAndView实例结合了
一个view 和一个 model Map,包含了bean name 和 通讯对象(像命令或者form,参考数据等等). View名称是非常高端的的配置&＃xff0c;不是通过bean name, 一个properties 文件就是通过你自己的ViewResolver.这个抽象的model Map 允许你在视图层面完成提取,没有任何的争辩:JSP,Velocity,或者其他,每一种都可以直接完整使用.这个model Map 还可以简单得得到适当的格式化数据的转换,像JSP 请求属性或者Velocity 模版模式.

3. Integration: Using a Different Web Framework with Spring
集成:用Spring一个不同web 框架

Many teams will try to leverage their investments in terms of know-how and tools, both for existing projects and for new ones. Concretely, there are not only a large number of books and tools for Struts but also a lot of developers that have experience with it. Thus, if you can live with Struts&＃39; architectural flaws, it can still be a viable choice for the web layer. The same applies to WebWork and other web frameworks.

许多开发团队将为他们已有的项目或者新的项目已经获得的期限和工具进行投资.这里没有像Struts那样大量的图书和工具&＃xff0c;但是同样我们有大量的拥有Spring开发技巧的开发人员.然而,如果你愿意生活在Struts的构架瑕疵中的话&＃xff0c;他将是你在web层开发不错的选择.当然&＃xff0c;其他应用也是一样.

If you don&＃39;t want to use Spring&＃39;s web MVC but intend to leverage other solutions that Spring offers, you can integrate the web framework of your choice with Spring easily. Simply start up a Spring root application context via its ContextLoaderListener, and access it via its ServletContext attribute (or Spring&＃39;s respective helper method) from within a Struts or WebWork action. Note that there aren&＃39;t any "plugins" involved, therefore no dedicated integration: From the view of the web layer, you&＃39;ll simply use Spring as a library, with the root application context instance as entry point.

如果你不想用Spring的 web MVC &＃xff0c;但是想借用Spring嫁接其他的解决方案,你可以非常简单地通过Spring 继承你自己的web 框架.你可以非常简单地通过ContextLoaderListener
启动一个Spring root application context, 并且,通过Struts 或者WebWork 的action 利用ServletContext 属性(或者Spring 的helper方法)存取它. 值得注意的是, 这里没有任何的
"plugins"被调用,因此没有专门的集成:来自web层的视图, 你可以简单的将Spring作为一个管理application context 实例入口点的类库.

All your registered beans and all of Spring&＃39;s services can be at your fingertips even without Spring&＃39;s web MVC. Spring doesn&＃39;t compete with Struts or WebWork in this usage, it just addresses the many areas that the pure web frameworks don&＃39;t, from bean configuration to data access and transaction handling. So you are able to enrich your application with a Spring middle tier and/or data access tier, even if you just want to use e.g. the transaction abstraction with JDBC or Hibernate.

所有你注册bean和Spring服务都可以在不需要Spring的web MVC的情况下都可以被你轻松掌握.Spring 不是和Struts ,WebWork这些应用进行竞争,它将作为一个纯web框架应用于
很多领域,因为它不需要配置数据存储和事务操作.所以,你可以利用Spring提供的中间层和数据存储层来丰富你的应用,甚至,你想用JDBC或者Hibernate进行事务抽象.

4. Feature Check List
特点核对列表

If just focussing on the web support, some of Spring&＃39;s unique features are:

如果聚焦于web 支持,Spring的一些显著特点是:

.Clear separation of roles: controller vs validator vs command object vs form object vs model object, DispatcherServlet vs handler mapping vs view resolver, etc.

清楚地角色分离:controller , validator , command object , form object , model object,和 DispatcherServlet , handler mapping vs view resolver, 等等

.Powerful and straightforward configuration of both framework and application classes as JavaBeans, including easy in-between referencing via an application context, e.g. from web controllers to business objects and validators.