基于Java的大學宿舍管理系統(tǒng)畢業(yè)設計外文翻譯及

1、職場大變樣社區(qū)（）：下載畢業(yè)設計成品全套資料，全部50元以下畢業(yè)設計說明書英文文獻及中文翻譯班 級： 學號： 姓 名： 學 院： 專 業(yè)： 指導教師： 2014年6月中北大學2014屆畢業(yè)設計英文文獻譯文jsp technologylevel: introductorybrett d. mclaughlin, sr. (brettnewi), author and editor, oreillyan old java technology hand and new enhydra partisan, the author urges developers to consider alterna

2、tives to javaserver pages (jsp) servlets when choosing an approach to coding web applications. jsp technology, part of suns j2ee platform and programming model, serves as a solution to the common dilemma of how to turn drab content into a visually appealing presentation layer. the fact is, web devel

3、opers arent uniformly happy with jsp technology. since many variations on the sun technology are now available, you can choose from a number of presentation technologies. this article takes an in-depth look at jsp coding and explores some attractive alternatives.presentation technology was designed

4、to transform plain ol raw web content into content wrapped in an attractive presentation layer. javaserver pages (jsp) technology, suns presentation model and part of the j2ee platform, has received significant attention. there are both advantages and disadvantages to using jsp technology, and web d

5、evelopers should be aware of the good and the bad - and know that they dont have to be limited to this single technology. in fact, these days a number of presentation technologies are available. this article begins by defining the problems presentation technologies were designed to solve. it then ex

6、amines the specific strengths and weaknesses of the jsp model. finally, it introduces some viable alternatives to suns presentation technology.the premisetoday, a decade beyond those fledgling windows applications, we are still dealing with this huge shift in the presentation paradigm. the woeful vi

7、sual basic and c programmers who remain now find themselves working either on back-end systems or windows-only applications, or they have added a web-capable language such as the java language to their toolbox. an application that doesnt support at least three of four ml-isms - such as html, xml, an

8、d wml - is considered shabby, if not an outright failure. and, of course, that means we all care very deeply about the ability to easily develop a web presentation layer.as it turns out, using the new internet, and all the languages we have at our disposal - java, c, perl, pascal, and ada, among oth

9、ers - hasnt been as easy as we might have hoped. a number of issues creep up when it comes to taking the programming languages everyone used for back-end systems and leveraging them to generate markup language suitable for a client. with the arrival of more options on the browser (dhtml and javascri

10、pt coding, for example), the increase in graphic artist talent in the web domain, and tools that could create complex interfaces using standard html, the demand for fancy user interfaces has grown faster than our ability to develop these front ends to our applications. and this has given rise to pre

11、sentation technology.presentation technology was designed to perform a single task: convert content, namely data without display details, into presentation - meaning the various user interfaces you see on your phone, palmpilot, or web browser. what are the problems that these presentation technologi

12、es claimed to solve? lets take a look.a bit of historybefore diving into an explanation of presentation technology, its helpful to fill in some details on the situation that led to the birth of the technology. just 10 short years ago, the term thin client was a novelty. we still lived in a world of

13、desktop applications, powered by wimpy 286 microprocessors with 14-inch monitors that we squinted at. boy, have times changed! now my desktop does nothing but power a web browser, while servers from sun, ibm, hp, compaq, and the rest churn out computations, business logic, and content. and that litt

14、le monitor? replaced by flat-screen, plasma, whopping 21- and 25-inch beauties. why? so we can see the intricate and complex html displays that serve as a front-end to these powerful applications. no longer does a clunky interface suffice; now we expect flashy graphics, moving images, color-coordina

15、ted presentations that would look good in any room in the house, and speedy rendering to boot.the promise of jsp technologynow, on to the specifics of jsp coding. the promise of jsp technology is to supply the designer and developer the only presentation technology they will ever need. jsp technolog

16、y is part of the j2ee platform, which is the strongest show of support sun can give one of its java products. to give you an idea of how prevalent this solution is, try running a search on jsp at ; youll find more books devoted to jsp technology than about almost any other single java api. before i

17、dive into the specific problems that jsp technology presents, you need a clear understanding of what it claims to do.the problemsive spelled out what a good presentation technology should provide, as well as the specific problems that jsp technology seeks to address. now, im ready to cut to the chas

18、e: jsp technology, while built on good ideas, presents quite a few problems. before you choose to use jsp coding in your applications (which you might still do), you should at least be aware of possible pitfalls.you should also be aware of a facet of the j2ee programming platform that is often ignor

19、ed: just because an api comes with the platform doesnt mean you have to use it. as silly as this sounds, many developers are struggling with the jsp, or ejb, or jms apis, thinking if they dont use these apis, their applications somehow wont really be j2ee applications. in fact, the platform boasts m

20、ore apis than most applications need. if you have problems with or doubts about jsp technology, you dont have to use it! take a close look at both the positives and the negatives before choosing to use jsp technology in your applications. lets take a look at some of the negatives.summaryi hope that

21、i have opened your eyes a bit about the advantages and disadvantages of jsp technology and that now you can look at jsp coding as one alternative among many presentation technologies. at this point, you might also be a bit skeptical about the entire j2ee programming model. if youre convinced to furt

22、her investigate the platform options, look for alternatives to jsp coding in apache cocoon, enhydra, and the various templating engines.finally, keep in mind that, despite all appearances to the contrary, this article isnt about recommending you use jsp or that you avoid it. i do intend to encourage

23、 you to peel back the layers of any technology to make sure its right for you. programming models are like examples; sometimes they make sense, and sometimes they dont. look around, find out what works best for you, and make the informed decision, rather than the quick one.have fun, and see you on t

24、he web!jsp技術作為一名 java 技術老手和新的 enhydra 擁護者，作者力勸開發(fā)人員在選擇設計 web 應用程序的途徑時，考慮一下 javaserver pages (jsp) servlet 以外的其他方法。實際上，web 開發(fā)人員也并非一致對 jsp 技術表示滿意。既然現(xiàn)在有 sun 技術的多種變體可以使用，所以您就可以在許多表示技術之間進行選擇。本文深入探討 jsp 編碼，并探究幾個有吸引力的替代方法。表示技術設計用來將平淡的拉丁文原始 web內容轉化為包裝在有吸引力的表示層中的內容。javaserver pages (jsp)技術，作為 sun 公司的表示模型和 j2e

25、e平臺的一部分，受到了極大關注。使用 jsp 技術有利有弊，web開發(fā)人員應知曉這些利弊 -懂得他們不必拘泥于這一技術。實際上，近來出現(xiàn)了許多表示技術。本文以表示技術所要解決的問題為開端，然后考察jsp 模型的特有優(yōu)勢和弱點。最后，介紹幾個可以代替 sun的表示技術的可行方案。前提 十年后的今天，作為雛形的 windows應用程序已經成為歷史，我們仍面臨著表示方法上的巨大轉變。悲慘的visual basic 和 c 程序員發(fā)現(xiàn)，他們現(xiàn)在只能編寫后端系統(tǒng)或僅用于windows 的應用程序，或者已在自己的工具箱中添加了能提供 web功能的語言，例如 java 語言。不支持四分之三以上 ml 語言（

26、如html、xml 和wml）的應用程序即使不被認為是完全失敗的，也會被認為是很低劣的。當然，這說明我們都很注重很容易地開發(fā)web 表示層的能力。結果是，使用新的因特網(wǎng)，以及我們熟悉的所有語言（java、c、perl、pascal、ada以及其他語言）都不像我們所希望的那么容易。當將每個人都使用的編程語言用于后端程序并生成適用于客戶機的標記語言時，會出現(xiàn)大量的問題。隨著瀏覽器提供更多的選項（例如dhtml 和 javascript 編碼）、web領域圖形藝術人才的增加、以及能夠使用標準 html生成復雜界面的工具的出現(xiàn)，對別具一格的用戶界面的需求比我們開發(fā)這些應用程序前端的能力增長得還要快。這

27、就導致了表示技術的興起。 表示技術設計用來執(zhí)行一項任務：將內容（即不帶顯示詳細信息的數(shù)據(jù)）轉換為表示- 即您在電話、掌上電腦或 web瀏覽器中看到的各種用戶界面。這些表示技術聲稱能夠解決哪些問題？讓我們來看一下。歷史點滴表示技術之前，介紹一些導致此技術產生的詳細背景資料很有幫助。僅僅在10年前，瘦客戶機還是一個很新的術語。那時我們還生活在臺式機應用程序的世界中，使用低級的286 微處理器，瞇著眼睛看 14英寸的顯示器。但是現(xiàn)在時代不同了，朋友！現(xiàn)在，我的臺式機除了運行web 瀏覽器之外什么也不干。我們使用 sun、ibm、hp、compaq和其他公司的服務器來運行計算、業(yè)務邏輯和內容。那個小顯

28、示器呢？它已被又大又漂亮的21 英寸和 25英寸等離子體平面顯示器所取代。為什么呢？因為這樣我們就可以觀看錯綜復雜的html 顯示，而這些 html顯示是強大的應用程序的前端。單調沉悶的界面已不能滿足要求；現(xiàn)在，我們希望看到華麗的圖形、移動的圖像、色彩協(xié)調的表示，不管哪個房間看上去都那么漂亮，并且能夠快速顯示出來。 編寫與修改 除了將內容和表示分離開來以外，衡量表示技術是否有用的另外一個因素則是它所免除的修改工作量。表示和內容的分離加大了內容開發(fā)人員的角色差別。程序員可將注意力集中在前面示例中的原始內容上，圖形藝術家或網(wǎng)站管理員則可將精力放在表示上。但是，在把藝術家設計的表示或標記取出并加入到

29、程序員編制的內容中時，還會出現(xiàn)一些角色交迭。 在最簡單的情況下，藝術家提供標記，開發(fā)人員提供代碼并將標記插入表示技術中。然后，應用程序“啟動”，內容會魔術般地變成一個用戶界面。當然，我們都知道，開發(fā)工作通常不會僅止于此。下一步是修訂和更改界面，并編制新的業(yè)務規(guī)則，這正是檢驗表示技術靈活性的地方。雖然更新輸入到表示層中的原始數(shù)據(jù)通常并不難，但是圖形藝術家就很難對他們的原始作品進行編輯。對表示層的更改是很常見的（我們都飽受過市場部門改這改那之苦）。所以，現(xiàn)在出現(xiàn)了這樣一個問題：設計人員應該從何處入手來更改他們的工作？是修改他們交給開發(fā)人員的原始標記語言頁嗎？可能不是。因為最可能的是，此頁很可能已插

30、入定制標記或代碼（jsp頁、模板引擎）、轉化為 java servlet、或者已變得面目全非了。通常，設計人員必須在原始頁上進行修改，并再次把此頁交給開發(fā)人員。開發(fā)人員必須把此頁再次轉化為表示技術所使用的特定格式。否則，設計人員就必須學會一種腳本語言，或至少懂得此頁中的哪些源代碼區(qū)域是禁止入內的。當然，這是一種容易出錯的、非常危險的方法。一旦您確定下來以一種表示技術支持內容和表示之間的明確分離，您就應確保改變表示所需的修改工作量限定在最小。jsp 技術的承諾 現(xiàn)在，我們來討論 jsp 編碼的具體內容。jsp技術承諾為設計人員和開發(fā)人員提供他們所需的最合適的表示技術。jsp技術是 j2ee 平臺的一部分，顯示了 sun 公司所能給予 java產品的最強大支持。為了使您對此解決方案的流行程度有一個概念，您可以試著在 上搜索一下“jsp”，您會發(fā)現(xiàn)，論述 jsp的書籍比論述其他任何一種 java api 的書籍都要多。在我深入討論 jsp技術存在的特定問題之前，