【正文】 many to hand over with each other with interface system of constitute foundation. According to the need of variable of the interface design, MVC hand over with each other constitute of system to resolve into model and see diagram, controller three part. Model(Model) is software processing problem logic at independence in outside manifestation under contents and form circumstance of inside abstract, packed the core data, logic of problem and function of calculation relation, independence in concrete of interface expression and I/O operation. See diagram(View) mean information and particular form demonstration of model data and logic relation and appearance to the customer. It acquire a manifestation 14 information from the model, there can be many for homology of information dissimilarity of manifestation form or see diagram. The controller(Controller) is a processing the customer hand over with software with each other operation of, its job is control provide model in any variety of dissemination, insure a customer interface among the model of rightness should contact。t any plugins involved, therefore no dedicated integration: From the view of the web layer, you39。t need to duplicate your business objects39。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 9 via Spring39。 首先對(duì) Hibernate進(jìn)行配置，只需要對(duì)系統(tǒng)自動(dòng)生成的，配置好數(shù)據(jù)庫(kù)連接的各種參數(shù)以及定義數(shù)據(jù)映射文件。在 Struts框架中，視圖主要由 JSP生成頁(yè)面完成，Struts提供豐富的 JSP標(biāo)簽庫(kù)，這有利于分開(kāi)表現(xiàn)邏輯和程序邏輯。在 Struts中，承擔(dān) MVC中控制器角色的是 ActionServlet?？刂破鳎?Controller）是處理用戶與軟件的交互操作的，其職責(zé)是控制提供模型中任何變化的傳播，確保用戶界面于模型間的對(duì)應(yīng)聯(lián)系；它接受用戶的輸入，將輸入反饋給模型， 進(jìn)而實(shí)現(xiàn)對(duì)模型的計(jì)算控制，是使模型和視圖協(xié)調(diào)工作的部件。在 Hibernate中有一個(gè)簡(jiǎn)單而直觀的 API，用于對(duì)數(shù)據(jù)庫(kù)所表示的對(duì)象執(zhí)行查詢。但是，在傳統(tǒng) J2EE應(yīng)用的開(kāi)發(fā)過(guò)程中也出現(xiàn)了一些問(wèn)題： 1）數(shù)據(jù)模型和邏輯模型之間的矛盾。 當(dāng)然 ,Spring 的自己的 web 支持和通常框架模式的細(xì)致完整 .然而， Spring替換 struts,webwork 或者其他的 web 方案非常的容易 .對(duì)于 Spring 的 web 支持或者不同的地方， Spring 允許你在 web 容器里面建立一個(gè)中間層，在測(cè)試環(huán)境或者標(biāo)準(zhǔn)獨(dú)立的應(yīng)用里面來(lái)設(shè)置重用你的商務(wù)邏輯 .還有在 J2EE 環(huán)境里面，你的商務(wù)邏輯不必依靠容器提供的服務(wù)，像 JTA ,EJB 的支持 .良好的構(gòu)架的 web 應(yīng)用可以運(yùn)行在任何容器上，如， Tomcat 或者 Resin. 值得注意的是， Spring 不是和已經(jīng)存在的解決方案進(jìn)行競(jìng)爭(zhēng) . 我們鼓勵(lì)結(jié)合標(biāo)準(zhǔn)的技術(shù)，如， Servlet, JSP, JTA, JNDI, JDBC, and JDO, 和非常匹配的工具，如， Hibernate, Velocity, Log4J, and Caucho39。 在和 struts 和 webwork 的對(duì)比上 ,Spring 是一個(gè)服務(wù)于所有層面的application framework:提供了 bean 的 配置基礎(chǔ)， AOP 的支持， JDBC 的提取框架，抽象事務(wù)支持，等等。 可訂制的操作 ,可訂4 制的視圖方案 :通過(guò) name/value Map 靈活的模型傳送 ,用一個(gè)簡(jiǎn)單的方法從簡(jiǎn)單到復(fù)雜操作映射和視圖方案策略 . 本地定制和主題方案 :Spring 沒(méi)有 taglib,完全支持于 JSPs， JSTL,不需要額外的連接 就可以支持 Velocity,等等 . 簡(jiǎn)單但是強(qiáng)大的 tag library 避免了HTML 產(chǎn)生的混亂 ,最大限度的靈活擴(kuò)展了標(biāo)記代碼 . 5 翻譯文稿 一種基于 Hibernate 和 Struts 的 J2EE 應(yīng)用開(kāi)發(fā)策略 本文分析了 Hibernate和 Struts的機(jī)制 ， 提出了一種基于 Hibernate和 Struts的 J2EE應(yīng)用開(kāi)發(fā)策略。 2 數(shù)據(jù)持久層及 Hibernate Hibernate是一個(gè)數(shù)據(jù)持久層框架，是一種實(shí)現(xiàn)對(duì)象和關(guān)系之間映射（ O/R Mapping）的工具，它對(duì) JDBC進(jìn)行了輕量級(jí)的對(duì)象封裝，使程序員可以使用對(duì)象編程思想來(lái)操作數(shù)據(jù)庫(kù)。 3 用 Struts實(shí)現(xiàn) MVC架構(gòu) MVC（ ModelViewController）由 Trygve Reenskaug提出，首先被應(yīng)用在 SmallTalk80環(huán)境中，是許多交互和界面系統(tǒng)的構(gòu)成基礎(chǔ)。如果用戶通過(guò)某個(gè)視圖的控制器改變了模型的數(shù)據(jù)，所有其它依賴于這些數(shù)據(jù)的視圖都應(yīng)反映到這些變化。它截取和 分發(fā)這些請(qǐng)求到相應(yīng)的動(dòng)作類（這些動(dòng)作類都是 Action類的子類）。 Struts框架沒(méi)有具體定義模型層的實(shí)現(xiàn)，在實(shí)際開(kāi)發(fā)中，模型層通常是和 業(yè)務(wù)邏輯緊密相連的，并且要對(duì)底層數(shù)據(jù)進(jìn)行操作。t particularly a web framework but a generic lightweight application framework with dedicated web support, and show the architectural differences 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 abstraction framework, abstract transaction support, etc. It is a very nonintrusive 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: . 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, Spring39。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 don39。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 a