【正文】 =format_sqltrue/property ! validate 只檢查結(jié)構(gòu) update 檢查結(jié)構(gòu)，更新或者創(chuàng)建表 create 每次啟動hibernate時，都要創(chuàng)建表 createdrop 啟動hibernate時創(chuàng)建表，當hibernate關閉時，刪除表 property name=update/property ! 3 聲明映射文件 mapping resource=tclemon/expresssystem/domain/ / mapping resource=tclemon/expresssystem/domain/ / mapping resource=tclemon/expresssystem/domain/ /mapping resource=tclemon/expresssystem/domain/ / /sessionfactory/hibernateconfiguration上面的代碼是Hibernate的配置文件。在主頁中，我們看到的是一個非常簡潔的頁面。如果查詢成功的話便跳轉(zhuǎn)到結(jié)果顯示頁面。主界面的結(jié)構(gòu)是一個frameSet的結(jié)構(gòu)。Bottom部分是最下面深藍的部分，顯示版權的相關信息。當點擊左邊的菜單時，在右邊的模塊顯示相應的頁面。當瀏覽器訪問系統(tǒng)時會先判斷用戶是否已經(jīng)登錄系統(tǒng)，同時判斷用戶訪問的頁面類型。在藍色的背景圖片上有兩個輸入框分別為用戶名輸入框和密碼輸入框。如果正確則登陸進入系統(tǒng)的主頁面，否則返回登陸頁面并且用紅色的字體提示用戶名或者密碼錯誤。同時還有新建員工的按鈕也看不見。即員工只能管理比自己等級低的員工。在操作時如果頁面?zhèn)鬟^來的用戶id的值是null則表示是新增操作，否則就是修改操作。當點擊保存按鈕是會彈出提示框如果保存成功會提示執(zhí)行成功，點擊確定會跳轉(zhuǎn)到用戶列表的頁面。當提交表單時會彈出提示窗口，如果提示操作成功，點擊確定會轉(zhuǎn)到員工列表頁面。 上圖顯示的用戶修改個人信息的界面。 上圖是員工修改自己的用戶名的界面。如果不存在則可以進行提交修改。當光標移開時異步提交輸入的原密碼到后臺判斷是否正確。并且必須按照寫明的要求輸入，兩次輸入的密碼必須一致才可以修改。3級以下的員工只能查看到網(wǎng)點列表。修改網(wǎng)點時同樣要回顯網(wǎng)點的相關信息。但是顯示數(shù)據(jù)的列表是一樣的。如果是退單則顯示退單管理，點擊超鏈接表示將快件的寄件相關的屬性與收件相關的屬性調(diào)換，運回到寄件地址。而點擊下方的改為問題件按鈕和改為退單的按鈕可以將快件狀態(tài)改為問題件和退單。 上圖顯示的是快件的添加頁面。并且在查詢結(jié)果顯示頁面中也可以進行上文提到的快件管理。 主要代碼的實現(xiàn)后臺有一個PageBean實體類管理分頁信息。并計算出其余的屬性的值后返回給前臺頁面。在下面的代碼中可以看出，后臺的pageBean對象放在了值棧中。%淺談分頁頁面的信息 %div id=PageSelectorBar div id=PageSelectorMemo 頁次：${pageNumber}/${pageCount}頁 amp。 總記錄數(shù)：${totalRecords}條 /div div id=PageSelectorSelectorArea a href=javascript:gotoPageNum(1) title=首頁 style=cursor: hand。 img src=${}/style/blue/images/pageSelector///a 轉(zhuǎn)到： select onchange=gotoPageNum() id=pn s:iterator begin=1 end=%{pageCount} var=num option value=${num} ${num}/option /s:iterator /select script type=text/javascript //將select值設定為當前頁的值 $(function() { $(pn).val(${pageNumber})。 // 方式二： $(pageForm).append(input type=39。 value=39。 //用于將查詢條件一直帶著 } /script/divPageBean的主要屬性和構(gòu)造函數(shù)如下。 //當前頁 private int pageSize。 //結(jié)束索引 //從數(shù)據(jù)庫查出來的 private int totalRecords。 = totalRecords。 endIndex=pageCount。 endIndex=10。測試以及根據(jù)測試結(jié)果修改代碼占軟件開發(fā)時間的絕大部分。我們要對系統(tǒng)進行比較全面的測試，并且根據(jù)測試的結(jié)果來看系統(tǒng)是否達到了設計要求。同時一班針對這種對表單的測試我們必須要設計好測試用例。不存在死鏈接的現(xiàn)象。本文列舉的是用戶密碼的修改功能模塊。測試的用例寫法采用的是等價劃分的方法。而兩次輸入的新密碼必須滿足一樣且在6到12位之間這樣的驗證邏輯。經(jīng)過對多個模塊的測試發(fā)現(xiàn)系統(tǒng)的每個模塊都可以正常工作。但是都通過網(wǎng)絡和書籍解決了。只有選擇一個選擇一個比較差的方案。就本系統(tǒng)來說，他已經(jīng)實現(xiàn)了設計的要求。就功能來說還是比較完善的。并且很多操作都會提示操作結(jié)果。本來用戶的等級應該根據(jù)他的職位來確定。還有就是瀏覽器的兼容性。其次在這個過程中溫習了一下很多課堂上學到的知識。8參考文獻[1]Java API 6[2]李剛：輕量級JavaEE企業(yè)應用實戰(zhàn)：電子工業(yè)出版社： [3]李剛：瘋狂Ajax講義：電子工業(yè)出版社：[4]BruceEckel:Java編程思想:機械工業(yè)出版社: [5]Rod Johnson：Expert OneonOne J2EE Design and Development：清華大學出版社：[6]福勒：企業(yè)應用架構(gòu)模式：機械工業(yè)出版社：[7]Robert C. Martin：敏捷軟件開發(fā)原則、模式與實踐：清華大學出版社：[8]張玉宏：Java從入門到精通：清華大學出版社：[9]張麗：Java Web應用詳解：北京郵電大學出版社：[10]王娜：Java Web項目開發(fā)案例教程：清華大學出版社：[11]聶艷明：Java EE開發(fā)技術與實踐教程：機械工業(yè)出版社：[12]劉玉紅：JavaScript+jQuery動態(tài)網(wǎng)頁設計案例課堂：清華大學出版社：[13]張鑫, 薛莉穎, 高茹：JavaScript網(wǎng)頁特效范例寶典：人民郵電出版社：[14]欒穎編：Java高級編程與應用/：清華大學出版社：[15]陳承歡：Java Web應用程序開發(fā)任務驅(qū)動式教程：清華大學出版社：[16]高洪巖：Java EE核心框架實戰(zhàn)：人民郵電出版社：[17]繆勇, 施俊, 李新鋒：Struts2+Spring3+Hibernate框架技術精講與整合案例/：清華大學出版社：[18]陸舟：Struts2技術內(nèi)幕:深入解析Struts2架構(gòu)設計與實現(xiàn)原理：機械工業(yè)出版社：[19]唐振明：JavaEE主流開源框架：電子工業(yè)出版社：[20]耿相宜：JavaEE架構(gòu)與程序設計：電子工業(yè)出版社：9 論文翻譯1 論文原文： Logistics and Supply Chain Management: An Area with a Strategic Service PerspectiveABSTRACT:Logistics and supply chain management is an area that evolved deeply in the past years, integrating developments of other areas of knowledge, both entrepreneurial and general. In this paper, a perspective of the evolution of logistics and supply chain management is somehow designed. Traditionally, one may find logistics and supply chain management in friction with marketing and claiming for its own space. Nowadays, it seems difficult to see internal (logistics) versus external (marketing) wars and different orientations between marketing and logistics because they are both service and relations oriented. Simple transactions have been substituted, long time ago, for sustainable relations in the area of logistics and supply chain management. Finally, a more service oriented logic has been the footprint of logistics and supply chain management in current days and not, as pretended for some current rows of investigation, a simple transaction approach under a goods dominant logic. Logistics and supply chain management is nowadays in parallel with an SD logic (service dominant logic) because it is an area where relations matter, where sustainable links between networks of panies are crucial and where service is key in order to acmodate the contemporary thoughts and practices in the area. The main purpose of the paper is to stress the point that logistics and supply chain management is an area of service and value creation (or cocreation) and not a simple area of goods exchange and simple transactions.1. Introduction and MethodologyThe structure of the paper is divided in three parts: a) the first one with the major evolutions of logistics and supply chain management (point number 3)。 vis with functional areas of panies) and always looking for other areas’ developments (specifically entrepreneurial and, also, general developments, ing from other areas of knowledge), catching ideas and integrating them in its own body of knowledge, logistics and supply chain management are presented today as being much more rich then they were in the past.It was much easier, of course, to acmodate to one of the paradigms which explain the internal dynamics of the enterprise itself—a school which emerged mainly from the operations management side [28].Meanwhile, the school ing from operations management was enriched with other lines of thought that have worked in parallel to place logistics clearly near the market paradigm and never stopped making the link between the place variable of the marketing and the logistic cli