Spring的web MVC构架模式.docVIP

Web MVC with the Spring Framework Juegen Hoeller 1. Introduction: Spring tho Application Framework When first confronted with the Spring Framework, one might be tempted to think: Oh no, not yet another web framrwork.This article will outline architecturaldifferences to Struts and 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 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. Of course, Springs own web support is nicely integrated with the frameworks general patterns. Nevertheless, replacing the web solution with Struts, WebWork, or the like is easy. Both with Springs 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 arehitected web applications to run in a simple container like Tomcat or Resin.Note that Spring doesn 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 Cauehos Hessian/Burlap. The framework is designed to grow with the needs of your applicattions, in terms of technology choice: For example you will probably use JTA via Springs JtaTransactionManager If you need distributed transactions but only then, as there are perfect replacements for single databases, like DataSourceTransactionManager or HibernateTransactionManager. 2. WebMVC: The Design of Springs Web Framework Spring s web framework is designed around a Dispatcherervlet that dispatches requests to handlers, with