【導(dǎo)讀】由金·海伊馮，Java技術(shù)顧問馬克·羅斯，組成部分的一項典型的軟件項目遵循。文章依據(jù)了一個JAVA程序語言模板的編碼協(xié)定，這。術(shù)相關(guān))過程中提出。尤其，它地址文件名字和組織，凹口，說明，指令，申明，scriptlets，表達(dá)方式，白色的空間，命名約定和編程慣例。請把全部反饋送到。風(fēng)格和有許多新特征預(yù)計逐步形成這些約定。話，這篇文章選擇將調(diào)控新JSP的約定為。他們改進(jìn)軟件人工制品的易讀性，明里注意到，術(shù)語"JSP程序段"被改為使用作為術(shù)語"JSP碎片"被超載。當(dāng)使JSP文件國際化時，我們推薦你通過他們的地點(diǎn)把JSP頁把歸類進(jìn)目錄。部分，我們將介紹關(guān)于JSP和標(biāo)記庫描述符文件的結(jié)構(gòu)。這條注釋只在服務(wù)器方面是可見的，因為它在JSP網(wǎng)頁面轉(zhuǎn)換期間被除去。是作者，日期和修正的版權(quán)申明，關(guān)于網(wǎng)開發(fā)者的JSP頁的一個標(biāo)識符和描述。說明部分提供簡明的關(guān)于JSP頁的目的的信息。制條件強(qiáng)加給那JSP頁指令可能被在相同的頁內(nèi)確定。

　　

【正文】 .jspf context root/WEBINF/jspf/subsystem path/ cascading style sheet .css context root/css/ JavaScript technology .js context root/js/ HTML page .html context root/subsystem path/ web resource .gif, .jpg, etc. context root/images/ tag library descriptor .tld context root/WEBINF/tld/ There are a few things to keep in mind when reading the table above. First, context root is the root of the context of the web application (the root directory inside a .war file). Second, subsystem path is used to provide refined logical grouping of dynamic and static web page contents. For a small web application, this may be an empty string. Third, we use the term JSP fragment to refer to a JSP page that can be included in another JSP page. Note that in the JSP Specification, the term JSP segment is used instead as the term JSP fragment is overloaded. JSP fragments can use either .jsp or .jspf as a suffix, and should be placed either in /WEBINF/jspf or with the rest of the static content, respectively. JSP fragments that are not plete pages should always use the .jspf suffix and should always be placed in /WEBINF/jspf. Fourth, though the JSP specification remends both .jspf and .jsp as possible extensions for JSP fragments, we remend .jspf as .jsf might be used by the JavaServer Faces specification. Finally, it is in general a good practice to place tag library descriptor files and any other nonpublic content under WEBINF/ or a subdirectory underneath it. In this way, the content will be inaccessible and invisible to the clients as the web container will not serve any files underneath WEBINF/. An optional wele file39。s name, as declared in the welefile element of the deployment descriptor (), should be if dynamic content will be produced, or if the wele page is static. When internationalizing JSP files, we remend that you group JSP pages into directories by their locale. For example, the US English version of would appear under /en_US/ whereas the Japanese version of the same file would appear under /ja_JP/. The Java Tutorial provides additional information about internationalizing Java code in generEnterpriseal, and the book Designing Applications with the J2EE Platform provides information about internationalization for web applications. File Organization A wellstructured source code file is not only easier to read, but also makes it quicker to locate information within the file. In this section, we39。ll introduce the structures for both JSP and tag library descriptor files. JSP File / JSP Fragment File A JSP file consists of the following sections in the order they are listed: Opening ments JSP page directive(s) Optional tag library directive(s) Optional JSP declaration(s) HTML and JSP code Opening Comments A JSP file or fragment file begins with a server side style ment: % Author(s): Date: Copyright Notice: @() Description: % This ment is visible only on the server side because it is removed during JSP page translation. Within this ment are the author(s), the date, and the copyright notice of the revision, an identifier and a description about the JSP page for web developers. The bination of characters @() is recognized by certain programs as indicating the start of an identifier. While such programs are seldom used, the use of this string does no harm. In addition, this bination is sometimes appended by $Id$ for the identification information to be automatically inserted into the JSP page by some version control programs. The Description part providesspan concise information about the purpose of the JSP page. It does not more than one paragraph. In some situations, the opening ments need to be retained during translation and propagated to the client side (visible to a browser) for authenticity and legal purposes. This can be achieved by splitting the ment block into two parts。 first, the clientside style ment: ! Author(s): Date: Copyright Notice: and then a shorter server side style ment: % @() Description: % JSP Page (s) A JSP page directive defines Directive attributes associated with the JSP page at translation time. The JSP specification does not impose a constraint on how many JSP page directives can be defined in the same page. So the following two Code Samples are equivalent (except that the first example introduces two extra blank lines in the output): Code Sample 1: %@ page session=false % %@ page import=.* % %@ page errorPage=/mon/ % If the length of any directive, such as a page directive, exceeds the normal width of a JSP page (80 characters), the directive is broken into multiple lines: Code Sample 2: %@ page session=false import=.* errorPage=/mon/ % In general, Code Sample 2 is the preferred choice for defining the page directive over Code Sample 1. An exception occurs when multiple Java packages need to be imported into the JSP pages, leading to a very long import attribute: %@ page session=false import=.*,.*, .*, .*, ... ... % In this scenario, breaking up this page directive like the following is preferred: % all attributes except import ones % %@ page ... % % import attributes start here % %@ page import=.* % %@ page import=.* % ... Note that in general the import statements follow the local code conventions for Java technology. For instance, it may generally be accepted that when up to three classes from the same packag