Author: buildbot Date: Tue Feb 18 02:20:44 2014 New Revision: 898339 Log: Production update by buildbot for tapestry
Modified: websites/production/tapestry/content/cache/main.pageCache websites/production/tapestry/content/configuration.html Modified: websites/production/tapestry/content/cache/main.pageCache ============================================================================== Binary files - no diff available. Modified: websites/production/tapestry/content/configuration.html ============================================================================== --- websites/production/tapestry/content/configuration.html (original) +++ websites/production/tapestry/content/configuration.html Tue Feb 18 02:20:44 2014 @@ -30,6 +30,7 @@ <script src='/resources/highlighter/scripts/shCore.js' type='text/javascript'></script> <script src='/resources/highlighter/scripts/shBrushJava.js' type='text/javascript'></script> <script src='/resources/highlighter/scripts/shBrushXml.js' type='text/javascript'></script> + <script src='/resources/highlighter/scripts/shBrushPlain.js' type='text/javascript'></script> <script type="text/javascript"> SyntaxHighlighter.defaults['toolbar'] = false; SyntaxHighlighter.all(); @@ -128,11 +129,11 @@ </div> </li></ul> </div><h1 id="Configuration-ConfiguringTapestry">Configuring Tapestry</h1><p>This page discusses all the ways in which Tapestry can be configured. Tapestry applications are configured almost entirely using Java, with very little XML at all.</p><p><strong>Contents</strong></p><p><style type="text/css">/*<![CDATA[*/ -div.rbtoc1392679261230 {padding: 0px;} -div.rbtoc1392679261230 ul {list-style: disc;margin-left: 0px;} -div.rbtoc1392679261230 li {margin-left: 0px;padding-left: 0px;} +div.rbtoc1392690038127 {padding: 0px;} +div.rbtoc1392690038127 ul {list-style: disc;margin-left: 0px;} +div.rbtoc1392690038127 li {margin-left: 0px;padding-left: 0px;} -/*]]>*/</style></p><div class="toc-macro rbtoc1392679261230"> +/*]]>*/</style></p><div class="toc-macro rbtoc1392690038127"> <ul class="toc-indentation"><li><a shape="rect" href="#Configuration-XMLconfiguration(web.xml)">XML configuration (web.xml)</a></li><li><a shape="rect" href="#Configuration-YourApplication'sModuleClass">Your Application's Module Class</a></li><li><a shape="rect" href="#Configuration-ConfigurationSymbolNames">Configuration Symbol Names</a></li><li><a shape="rect" href="#Configuration-SettingComponentParameterDefaults">Setting Component Parameter Defaults</a></li><li><a shape="rect" href="#Configuration-ConfiguringIgnoredPaths">Configuring Ignored Paths</a></li><li><a shape="rect" href="#Configuration-ConfiguringContentTypeMapping">Configuring Content Type Mapping</a></li><li><a shape="rect" href="#Configuration-SettingExecutionModes">Setting Execution Modes</a></li><li><a shape="rect" href="#Configuration-SegregatingApplicationsIntoFolders">Segregating Applications Into Folders</a></li></ul> </div><h2 id="Configuration-XMLconfiguration(web.xml)">XML configuration (web.xml)</h2><p>Tapestry runs on top of the standard Java Servlet API. To the servlet container, such as Tomcat, Tapestry appears as a <em>servlet filter</em>. This gives Tapestry great flexibility in matching URLs without requiring lots of XML configuration.</p><p>Although most configuration is done with Java, a small but necessary amount of configuration occurs inside the servlet deployment descriptor, WEB-INF/web.xml. Most of the configuration is boilerplate, nearly the same for all applications.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>web.xml (partial)</b></div><div class="codeContent panelContent pdl"> <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[<!DOCTYPE web-app @@ -433,7 +434,21 @@ div.rbtoc1392679261230 li {margin-left: </div> <div style="border-right: 20px solid #D8E4F1;border-left: 20px solid #D8E4F1;"> -<p> </p></div><p>Tapestry relies on an underlying client-side JavaScript infrastructure framework to handle DOM manipulation, event handling, and Ajax requests. Through Tapestry 5.3, the foundation was <a shape="rect" class="external-link" href="http://http//prototypejs.org/" >Prototype</a>. In 5.4, support for <a shape="rect" class="external-link" href="http://jquery.org/" >jQuery</a> has been added, and it is possible to add others. This symbol defines a value that is used to select a resource that is provided to the ModuleManager service as a JavaScriptModuleConfiguration to provide a specific implementation of the <code>t5/core/dom</code> module. Tapestry 5.4 directly supports "prototype" or "jquery". To support other foundation frameworks, override this symbol value and supply your own module configuration.</p><p>In Tapestry 5.4, this defaults to "prototype" for compatibility with 5.3. This will likely change in 5.5 to default to "jquery". At some point in the future, Prot otype support may no longer be present.</p><h3 id="Configuration-tapestry.min-gzip-size">tapestry.min-gzip-size</h3><p>The minimum stream size necessary for Tapestry to use GZIP compression on the response stream. See <a shape="rect" href="response-compression.html">Response Compression</a> for more details.</p><h3 id="Configuration-tapestry.omit-generator-meta">tapestry.omit-generator-meta</h3><p>If "true", then the <meta> tag that Tapestry normally writes into the <head>, identifying the Tapestry version, will be omitted. Use this when you do not wish to advertise your application's use of Tapestry.</p><h3 id="Configuration-tapestry.page-pool.active-window">tapestry.page-pool.active-window</h3> +<p> </p></div><p>Tapestry relies on an underlying client-side JavaScript infrastructure framework to handle DOM manipulation, event handling, and Ajax requests. Through Tapestry 5.3, the foundation was <a shape="rect" class="external-link" href="http://http//prototypejs.org/" >Prototype</a>. In 5.4, support for <a shape="rect" class="external-link" href="http://jquery.org/" >jQuery</a> has been added, and it is possible to add others. This symbol defines a value that is used to select a resource that is provided to the ModuleManager service as a JavaScriptModuleConfiguration to provide a specific implementation of the <code>t5/core/dom</code> module. Tapestry 5.4 directly supports "prototype" or "jquery". To support other foundation frameworks, override this symbol value and supply your own module configuration.</p><p>In Tapestry 5.4, this defaults to "prototype" for compatibility with 5.3. This will likely change in 5.5 to default to "jquery". At some point in the future, Prot otype support may no longer be present.</p><h3 id="Configuration-tapestry.lenient-date-format">tapestry.lenient-date-format</h3> + + <div class="aui-message hint shadowed information-macro"> + <p class="title">Added in 5.4</p> + <span class="aui-icon icon-hint">Icon</span> + <div class="message-content"> + + + </div> + </div> + +<div style="border-right: 20px solid #D8E4F1;border-left: 20px solid #D8E4F1;"> + +<p>When set to true, the DateField component will be lenient about date calculations, for example allowing a January 32 date as input and automatically converting it to February 1. When false (the default), only valid dates may be entered.</p> +</div><p><br clear="none">If false (the default)</p><h3 id="Configuration-tapestry.min-gzip-size">tapestry.min-gzip-size</h3><p>The minimum stream size necessary for Tapestry to use GZIP compression on the response stream. See <a shape="rect" href="response-compression.html">Response Compression</a> for more details.</p><h3 id="Configuration-tapestry.omit-generator-meta">tapestry.omit-generator-meta</h3><p>If "true", then the <meta> tag that Tapestry normally writes into the <head>, identifying the Tapestry version, will be omitted. Use this when you do not wish to advertise your application's use of Tapestry.</p><h3 id="Configuration-tapestry.page-pool.active-window">tapestry.page-pool.active-window</h3> <div class="aui-message problem shadowed information-macro"> <p class="title">Deprecated since 5.2</p>