【導(dǎo)讀】借助于J2EE規(guī)范中包含的多項技術(shù)：EnterpriseJavaBean、Java. Servlets、JavaServerPages、JavaMessageService等，開發(fā)。但是，在傳統(tǒng)J2EE應(yīng)用的開發(fā)過程中也出現(xiàn)了一些問題：。目前使用的數(shù)據(jù)庫基本上都是關(guān)系型數(shù)據(jù)庫，操作，降低了編程的效率以及系統(tǒng)的可維護性；用，但是使用EJB容器進行開發(fā)和調(diào)試需要耗費大量時間。為了降低代碼的耦合性，提。它不僅提供了從Java類到數(shù)據(jù)表的映射，也提供了數(shù)據(jù)查詢和恢復(fù)機制。據(jù)表之間的關(guān)系解釋為Java對象之間的繼承及包含等關(guān)系。在Hibernate中有一個簡單而直觀的API，用于對數(shù)據(jù)庫所表示的對象執(zhí)行查詢。或修改這些對象，只需在程序中與它們進行交互，然后告訴Hibernate保存即可。把表示模型數(shù)據(jù)及邏輯關(guān)系和狀態(tài)的信息及特定形式展示給用戶。時發(fā)生了何種數(shù)據(jù)變化，控制器都會將變化通知所有的視圖，導(dǎo)致顯示的更新。在Struts中，承擔(dān)MVC中控制器角色的是。在Struts框架中，視圖主要由JSP生。的服務(wù)，像JTA,EJB的支持。良好的構(gòu)架的web應(yīng)用可以運行在任何容器上，如，Tomcat

　　

【正文】 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. Regarding views: 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, 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 plete 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. If you don39。t want to use Spring39。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 Spring39。s respective helper method) from within a Struts or WebWork action. Note that there aren39。t any plugins involved, therefore no dedicated integration: From the view of the web layer, you39。ll simply use Spring as a library, with the root application context instance as entry point. All your registered beans and all of Spring39。s services can be at your fingertips even without Spring39。s web MVC. Spring doesn39。t pete with Struts or WebWork in this usage, it just addresses the many areas that the pure web frameworks don39。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 . the transaction abstraction with JDBC or Hibernate. If just focussing on the web support, some of Spring39。s unique features are: .Clear separation of roles: controller vs validator vs mand object vs form object vs model object, DispatcherServlet vs handler mapping vs view resolver, etc. .Powerful and straightforward configuration of both framework and application classes as JavaBeans, including easy inbetween referencing via an application context, . from web controllers to business objects and validators. .Adaptability, nonintrusiveness: Use whatever Controller subclass you need (plain, mand, form, wizard, multi action, or a custom one) for a given scenario instead of deriving from Action/ActionForm for everything. .Reusable business code, no need for duplication: You can use existing business objects as mand or form objects instead of mirroring them in special ActionForm subclasses. .Customizable binding and validation: type mismatches as applicationlevel validation errors that keep the offending value, localized date and number binding, etc instead of Stringonly form objects with manual parsing and conversion to business objects. Customizable handler mapping, customizable view resolution: flexible model transfer via name/value Map, handler mapping and view resolution strategies from simple to sophisticated instead of one single way. With in the J2 the EE the application very widespread customer register process for example, elucidation abovementioned system structure is how concrete usage. The process of register is very clear: Customer from register page importation register information, system to register the information carry on verification, if exactitude success register, otherwise hint correspond mistake information. In the development process, the usage Eclipse be used as development environment and added to carry to provide to the Struts and the Hibernate in the meantime better control and support of three square plugin MyEclipse, Web server usage Tomcat, the database chose to use Mysql. Carry on an allocation to the Hibernate first, need to the system auto the born . xml carry on modification, allocation good database conjunction of various parameter and definition the data reflect to shoot a document. Because the Hibernate take of conjunction pond main used for test, the function isn39。t very good, can pass JNDI will it modification is usage Tomcat of conjunction pond.