【導讀】畢業(yè)設計（論文）-基于Struts+Spring+Hibernate架。構的藥品銷售系統(tǒng)研究與實現(xiàn)。學校代碼10567中圖分類號專業(yè)代。本科生畢業(yè)論文設計。姓名Xxx部系信息工程學院專業(yè)信息與計算科學。年級2021級EmailXxx指導教師劉x. Xxx教務處制2021年4月2日。2系統(tǒng)總體框架4. 53業(yè)務邏輯層實現(xiàn)17. 譯文原件復印件31. 論文結合藥品銷售系統(tǒng)多層次體系結構發(fā)展的現(xiàn)狀探討Struts2xSpring和。Hibernate框架方法本文以基于J2EE體系的Web開發(fā)方法為探討的基線首先。從ServletJsp技術原理到結合這兩種技術進行Web開發(fā)的Model1和Model2. 設計再到實現(xiàn)Model2的Struts架構內(nèi)部機制進行探討其次對持久層的設計進行。臺和后臺區(qū)可為發(fā)布為提供管理的服務系統(tǒng)是基于BSBrowserServer瀏覽器客。該系統(tǒng)的用戶為藥品銷售企業(yè)每日需要發(fā)布一些最新藥品信息和提供在線。求為該藥品銷售系統(tǒng)具有一般藥品銷售系統(tǒng)的功能同時具有管理員對后臺數(shù)據(jù)。的處理功能如新藥品上架下架和輸入價格及調整會員價格等。根據(jù)藥品銷售系統(tǒng)管理的實際需求在首頁中能顯示最熱賣的藥品口碑好的

　　

【正文】 和自定義的服務 Struts 2 提供一個名叫 ActionSupport 的基類實現(xiàn)一般使用的接口雖然 Action 接口不是必須的任何使用 execute 方法的 POJO 對象可以被當作 Struts 2 的 Action 對象使用 Validation Struts 1 支持手動驗證憑借 ActionForm 的 validate 方法或者通過擴展的公用驗證器類可以有不同的驗證上下文未相同的類但是不能不能包括驗證子對象 Struts 2 支持手動驗證憑借 validate 方法和 XWork 驗證框架 Xwork 驗證框架支持一連串的驗證子屬性使用的驗證了屬性類的類型和嚴正上下文而定義Threading Model Struts 1 Action 類是單例類因只有一個示例控制所有的請求單例類策略造成了一定的限制且給開發(fā)帶來了額外的煩惱 Action 資源必須是程安全或者同步的 Struts 2 Action 對象每一個請求都實例化對象所以沒有程安全的問題實踐中servlet 容器生許多丟的對象對于每一個請求多于一個的對象并不影響垃圾收集 Testability 測試 Struts 1 的主要障礙是 execute 方法暴露了 Servlet API 第三方的擴展 Struts 測試用例提供 Struts 1 的集合對象 Struts 2 的 Action 可以通過實例化 Action 測試設置屬性然后調用方法依賴注入的支持也是測試變得更簡單 Harvesting Input Struts 1 使用 ActionForm 對象捕獲輸入 Action 一樣所有的 ActionForm 必須擴展基類其他的 JavaBean不能作 ActionForm使用開發(fā)者經(jīng)常創(chuàng)建多余的類捕獲輸入 DynaBeans 可 以被用替代 ActionForm 的類創(chuàng)建但是開發(fā)者可以重新描述已經(jīng)存在的 JavaBean Struts 2 Action 屬性作輸入屬性排除第二個輸入對象的需要輸入屬性可能有豐富的對象類型這些類型有他們自己的屬性 Action 的屬性可以通過標簽庫訪問 Struts 2也支 ActionForm形式豐富的對象類型包含業(yè)務或者域對象可以被當作輸入或者輸出對象使用饃型驅動特性簡化標簽對 POJO 輸入對象的引用 Expression Language Struts 1 整和 JSTL 所以它使用 JSTL 的表達式語言表達式語言有基本 的圖形對象移動但是相對很弱的集合和被索引的屬性支持 Struts 2 使用 JSTL 但是框架也支持更大和更靈活的表達式叫做對象圖形符號語言 OGNL Binding values into views Struts 1 使用標準 JSP 機制來綁定對象到頁面上下文 Struts 2 使用ValueStack 技術了標簽庫可以不用鏈接你的視圖到對象的表現(xiàn)類型訪問值ValueStack 策略允許重用視圖 Type Conversion Struts 1 的 ActionForm 屬性經(jīng)常都是 String 的 Struts 1 使用CommonsBeanutils 類型轉換轉換每一個類不是每一個實例配置 Struts 2 使用OGNL 類型轉換框架包含轉換器基本的和共同的對象類型和原始類型 Control Of Action Execution Struts 1 支持獨立的請求處理器對于每一個模型但是所有在模型中的Action 必須共享同一個生命周期 Struts 2 支持在每一個 Action 基礎上憑借攔截棧創(chuàng)建不同的生命周期自定義?？梢员粍?chuàng)建且使用不同的所需 的ActionApache Struts 2 Apache Struts 2 is an elegant extensible framework for creating enterpriseready Java web applications The framework is designed to streamline the full development cycle from building to deploying to maintaining applications over time The Apache Software Foundation 41 Introduction Apache Struts is an opensource framework that is used for developing Java web application Originally developed by the programmer and author Craig R McClanahan this was later taken over by the Apache Software Foundation in 2021 Struts have provided an excellent framework for developing application easily by anizing JSP and Servlet based on HTML formats and Java code Strut1 with all standard Java technologies and packages of Jakarta assists to create an extensible development environment However with the growing demand of web application Strut 1 does not stand firm and needs to be changed with demand This leads to the creation of Strut2 which is more developer friendly with features like Ajax rapid development and extensibility History of Struts 2 Since arriving on the scene in 2021 Apache Struts has enjoyed a very successful run by most any standard helping to build many if not most of the Javabased web applications deployed today Its history tells of how Struts provided a solid framework to anize the mess of JSP and Servlets to make developing applications which used mostly servergenerated HTML with a touch JavaScript for clientside validation easier to develop and maintain As time moved forward and customer demands of web applications grew and grew Struts 1 pretty much stayed the same leaving more and more plumbing to the web developer At JavaOne 2021 several of the Struts developers sat down with a few Struts users to discuss the future of Struts and came up with the Struts Ti proposal which described a framework that brought together a lot of good things that were developing in the web framework munity The problem is that the Struts 1 code base didnt lend itself to drastic improvements and its feature set was rather limited particularly lacking in features such as Ajax rapid development and extensibility At the same time they also met developers from other frameworks such as the Spring WebFlow project and started discussing around an idea of the possibility of bining efforts into one framework However there were several obstacles and questions about project ownership brand and identity that seems to block the progress Fortunately developers from Struts and WebWork did not lose the momentum and suggested the idea of a merger At that time Struts developers were also working on Apache Shale a web framework based off JSF as a Struts subproject along side Struts Action 1 now called Struts 1 and Struts Action 2 the graduated WebWork 2 code Unfortunately these subprojects were confusion to the developer and user munity accustomed to the name Struts referring to a single framework After an attempt to unify the Struts Action 2 and Shale subprojects into a single Struts 2 framework the Shale developers felt it would be better if they were their own top level project where they are today Struts Action 2 was soon after renamed to simply Struts 2 Today the Apache Struts project has two major versions of its framework but it is one actionbased framework project WebWork continues to deliver patch releases and will certainly continue to do so until Struts 2 goes on but all new development takes place on the Struts 2 code Since the initial appearance the Struts 2 code has added major features including a plugin framework new APIs and better Ajax tags and will still keep on improving 42 Struts 2 features The MVC Architecture Inherited from Struts 1 Struts 2 is also an open source framework used for developing J2EE web applications using Model View Controller design pattern The main aim of the MVC architecture is to separate the business logic and application data from the presentation data to the user Here are the reasons why we should use the MVC design pattern They are reusable When the problems recurs there is no need to invent a new solution we just have to follow the pattern and adapt it as necessary They are expressive By using the MVC design