【正文】 b MVC frameworks don39。s services can be at your fingertips even without Spring39。s point of view, you39。s respective helper method) from within a Struts or WebWork action. Note that there aren39。t want to use Spring39。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 mand or form, containing reference data). 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 plete abstraction of the view technology, without any hassle. Any renderer can be integrated directly, whether JSP, Velocity, or any other rendering technology. The model Map is simply transformed into an appropriate format, such as JSP request attributes or a Velocity template model.. Pluggability of other MVC implementations There are several reasons why some projects will prefer to use other MVC implementations. Many teams expect to leverage their existing investment in skills and tools. In addition, there is a large body of knowledge and experience avalailable for the Struts framework. Thus, if you can live with Struts39。t need to duplicate your business objects39。s no need to implement an interface or derive from a base class. Spring39。t have a form, you don39。s MVC implementation is not just any implementation, it provides a clean separation between domain model code and web forms and allows you to use all the other features of the Spring Framework like validation. Spring39。s Web package provides basic weboriented integration features, such as multipart functionality, initialization of contexts using servlet listeners and a weboriented application context. When using Spring together with WebWork or Struts, this is the package to integrate with. Spring39。 畢 業(yè) 設(shè) 計（論 文） 外文文獻(xiàn)翻譯 系 別： XXXXXXXXXXXX 專 業(yè)： XXXXXXXXXXXX 班 級： XXXXXXXXXXXX 學(xué)生姓名： XXX 導(dǎo)師姓名： XXXX 職稱： XXXX 起止時間： 2021 年 3 月 2 日 至 2021 年 6 月 12 日 英文原文 Spring contains a lot of functionality and features, which are wellanized in seven modules shown in the diagram below. This section discusses each the of modules in turn. The Core package is the most fundamental part of the framework and provides the Dependency Injection features allowing you to manage bean container functionality. The basic concept here is the BeanFactory, which provides a factory pattern removing the need for programmatic singletons and allowing you to decouple the configuration and specification of dependencies from your actual program logic. On top of the Core package sits the Context package, providing a way to access beans in a frameworkstyle manner, somewhat resembling a JNDIregistry. The context package inherits its features from the beans package and adds support for text messaging using . resource bundles, eventpropagation, resourceloading and transparent creation of contexts by, for example, a servlet container. The DAO package provides a JDBCabstraction layer that removes the need to do tedious JDBC coding and parsing of databasevendor specific error codes. Also, the JDBC package provides a way to do programmatic as well as declarative transaction management, not only for classes implementing special interfaces, but for all your POJOs (plain old java objects). The ORM package provides integration layers for popular objectrelational mapping APIs, including JDO, Hibernate and iBatis. Using the ORM package you can use all those O/Rmappers in bination with all the other features Spring offers, like simple declarative transaction management mentioned before. Spring39。s AOP package provides an AOP Alliance pliant aspectoriented programming implementation allowing you to define, for example, methodinterceptors and pointcuts to cleanly decouple code implementing functionality that should logically speaking be separated. Using sourcelevel metadata functionality you can incorporate all kinds of behavioral information into your code, a little like .NET attributes. Spring39。s Web MVC package provides a ModelViewController implementation for webapplications. Spring39。s web MVC framework is designed around a DispatcherServlet that dispatches requests to handlers, with configurable handler mappings, view resolution, locale and theme resolution as well as support for upload files. 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, for example AbstractController, AbstractCommandController and SimpleFormController. Application controllers will typically be subclasses of those. Note that you can choose an appropriate base class: If you don39。t nee