📄 package-summary.html
字号:
<pre>
<%@ taglib uri="/WEB-INF/struts-tiles.tld" prefix="tiles" %>
<HTML>
<HEAD>
<link rel="stylesheet" href="<%=request.getContextPath()%>/layouts/stylesheet.css"
type="text/css"/>
<title><tiles:getAsString name="title"/></title>
</HEAD>
<body>
<table border="0" width="100%" cellspacing="5">
<tr>
<td colspan="2"><tiles:insert attribute="header" /></td>
</tr>
<tr>
<td width="140" valign="top">
<tiles:insert attribute='menu' />
</td>
<td valign="top" align="left">
<tiles:insert attribute='body' />
</td>
</tr>
<tr>
<td colspan="2">
<tiles:insert attribute="footer" />
</td>
</tr>
</table>
</body>
</html>
</pre>
<p>The layout is declared in a JSP page (ex: /layouts/classicLayout.jsp).
It can be used in conjunction with the tag described in "<a href="#doc.InsertPageWithAttributes">Insert
a page passing some attributes</a>". </p>
</div>
</div>
<div class="section">
<h2>Definitions</h2>
<p>A definition associates a logical name with the URL of a Tiles to be inserted
and some attribute values. A definition doesn't insert the Tiles. This is
done later using the definition name. A definition name can be inserted
as often as you want in your site, making it easy to reuse a Tiles. </p>
<p>A definition can extend another definition and overload some attributes
or add new ones. This makes easy factorization of definitions differing
by some attributes. For example, you can define a master definition declaring
the main header, menu, footer, and a default title. Then let each of your
page definitions extend this master definition and overload the title and
the body.</p>
<p>Definitions can be declared in a JSP page, or in one or more centralized
files. To enable the definitions from centralized files, you need to initialize
the "definitions factory&&quot; which will parse the definitions from the files
and provide them to the Tiles framework.</p>
<div class="subsection1">
<h3>Enabling Definition Factory</h3>
<p>To enable Tiles definitions described in one or more files, you need to write these files and to initialize the definition factory. </p>
<p>Initialization is different depending on the Struts version you use,
or if you do not use Struts at all.</p>
<div class="subsection2">
<h4>Struts1.1</h4>
<p>Use the Tiles plug-in to enable Tiles definitions. This plug-in creates
the definition factory and passese it a configuration object populated
with parameters. Parameters can be specified in the web.xml file or
as plug-in parameters. The plug-in first reads parameters from web.xml,
and then overloads them with the ones found in the plug-in. All parameters
are optional and can be omitted. The plug-in should be declared in each
struts-config file:</p>
<pre>
<plug-in className=&&quot;org.apache.struts.tiles.TilesPlugin&&quot; >
<set-property property=&&quot;definitions-config&&quot;
value=&&quot;/WEB-INF/tiles-defs.xml,
/WEB-INF/tiles-tests-defs.xml,/WEB-INF/tiles-tutorial-defs.xml,
/WEB-INF/tiles-examples-defs.xml&&quot; />
<set-property property=&&quot;moduleAware&&quot; value=&&quot;true&&quot; />
<set-property property=&&quot;definitions-parser-validate&&quot; value=&&quot;true&&quot; />
</plug-in>
</pre>
<ul>
<li>definitions-config: (optional) <ul>
<li>Specify configuration file names. There can be several comma separated file names (default: ?? )</li>
</ul>
</li>
<li>definitions-parser-validate: (optional)
<ul>
<li>Specify if XML parser should validate the Tiles configuration
file
<ul>
<li>true : validate. DTD should be specified in file header (default)</li>
<li>false : no validation </li>
</ul>
</li>
</ul>
</li>
<li>moduleAware: (optional)
<ul>
<li>Specify if the Tiles definition factory is module aware. If true (default),
there will be one factory for each Struts module.
If false, there will be one common factory for all module. In this later case,
it is still needed to declare one plugin per module. The factory will be
initialized with parameters found in the first initialized plugin (generally the
one associated with the default module).
<ul>
<li>true : Tiles framework is module aware </li>
<li>false :Tiles framework has one single factoy shared among modules (default)</li>
</ul>
</li>
</ul>
</li>
<li>tilesUtilImplClassname: (optional - for advanced user)
<ul>
<li>Specify The classname of the TilesUtil implementation to use. The specified class should
be a subclass of TilesUtilStrutsImpl. This option disable the moduleAware option.
<br>Specifying &&quot;TilesUtilStrutsImpl&&quot; is equivalent to moduleAware = false.</br>
<br>Specifying &&quot;TilesUtilStrutsModuleImpl&&quot; is equivalent to moduleAware = true.</br>
This option is taken into account only once, when it is first encountered. To avoid problems,
it is advice to specify the same values in all TilesPlugin declaration.
</li>
</ul>
</li>
</ul>
<p>The TilesPlugin class creates one definition factory for each struts module.
</p>
<p>
If the flag moduleAware is false, only one shared factory is created for all modules.
In this later case, the factory is initialized with parameters found in the first plugin.
The plugins should be declared in all modules, and the moduleAware flag should be
the same for the entire application.</p>
<p>
Paths found in Tiles definitions are relative to the main context.</p>
<p>You don't need to specify a TilesRequestProcessor, this is automatically
done by the plug-in. If, however, you want to specify your own RequestProcessor,
it should extend the TilesRequestProcessor. The plug-in checks this
constraint.</p>
</div>
<div class="subsection2">
<h4>Struts1.0.x</h4>
<p>You need to use a special servlet extending the Struts servlet. This is specified in the web.xml file of your application:</p>
<pre>
<servlet>
<servlet-name>action</servlet-name>
<servlet-class>org.apache.struts.tiles.ActionComponentServlet</servlet-class>
<!-- Tiles Servlet parameter
Specify configuration file names. There can be several comma
separated file names
-->
<init-param>
<param-name>definitions-config</param-name>
<param-value>/WEB-INF/tiles-defs.xml</param-value>
</init-param>
<!-- Tiles Servlet parameter
Specify if XML parser should validate the Tiles configuration file(s).
true : validate. DTD should be specified in file header.
false : no validation
-->
<init-param>
<param-name>definitions-parser-validate</param-name>
<param-value>true</param-value>
</init-param>
...
</servlet>
</pre>
</div>
<div class="subsection2">
<h4>Without Struts</h4>
<p>Tiles can be used without Struts. To initialize the definition factory, you can use the provided servlet. Declare it in the web.xml file of your application:</p>
<pre>
<servlet>
<servlet-name>action</servlet-name>
<servlet-class>org.apache.struts.tiles.TilesServlet</servlet-class>
<init-param>
<param-name>definitions-config</param-name>
<param-value>/WEB-INF/tiles-defs.xml</param-value>
</init-param>
<init-param>
<param-name>definitions-parser-validate</param-name>
<param-value>true</param-value>
</init-param>
...
</pre>
<p>The parameters are the same as for Struts1.1 or 1.0.</p>
</div>
</div>
<div class="subsection1">
<h3>Definition File Syntax</h3>
<p>The definition file syntax can be found in the
<a href="http://jakarta.apache.org/struts/dtds/tiles-config_1_1.dtd">tiles-config_1_1.dtd file</a>.
</p>
<p>Following is a simple example:</p>
<pre>
<!DOCTYPE tiles-definitions PUBLIC
&&quot;-//Apache Software Foundation//DTD Tiles Configuration//EN&&quot;
&&quot;http://jakarta.apache.org/struts/dtds/tiles-config_1_1.dtd&&quot;>
<!-- Definitions for Tiles documentation -->
<tiles-definitions>
<!-- ========================================================== -->
<!-- Master definition -->
<!-- ========================================================== -->
<!-- Main page layout used as a root for other page definitions -->
<definition name=&&quot;site.mainLayout&&quot; path=&&quot;/layouts/classicLayout.jsp&&quot;>
<put name=&&quot;title&&quot; value=&&quot;Tiles Blank Site&&quot; />
<put name=&&quot;header&&quot; value=&&quot;/tiles/common/header.jsp&&quot; />
<put name=&&quot;menu&&quot; value=&&quot;site.menu.bar&&quot; />
<put name=&&quot;footer&&quot; value=&&quot;/tiles/common/footer.jsp&&quot; />
<put name=&&quot;body&&quot; value=&&quot;/tiles/body.jsp&&quot; />
</definition>
<!-- ========================================================== -->
<!-- Index page definition -->
<!-- ========================================================== -->
<!-- This definition inherits from the main definition.
It overloads the page title and the body used.
Use the same mechanism to define new pages sharing common
properties (here header, menu, footer, layout)
-->
<definition name=&&quot;site.index.page&&quot; extends=&&quot;site.mainLayout&&quot; >
<put name=&&quot;title&&quot; value=&&quot;Tiles Blank Site Index&&quot; />
<put name=&&quot;body&&quot; value=&&quot;/tiles/body.jsp&&quot; />
</definition>
</tiles-definition>
</pre>
</div>
<div class="subsection1">
<h3>Debugging</h3>
<p>To debug a page made of Tiles, you can use following advices:</p>
<ul>
<li>Check each Tiles separatly. Try to access nested Tiles directly to test
if thes work properly.</li>
<li>Enable Tiles logging. See the commons-logging package help.</li>
</ul>
</div>
</div>
</div>
<P>
<HR>
<!-- ========== START OF NAVBAR ========== -->
<A NAME="navbar_bottom"><!-- --></A><TABLE BORDER="0" WIDTH="100%" CELLPADDING="1" CELLSPACING="0">
<TR>
<TD COLSPAN=2 BGCOLOR="#EEEEFF" CLASS="NavBarCell1">
<A NAME="navbar_bottom_firstrow"><!-- --></A><TABLE BORDER="0" CELLPADDING="0" CELLSPACING="3">
<TR ALIGN="center" VALIGN="top">
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <A HREF="../../../../overview-summary.html"><FONT CLASS="NavBarFont1"><B>Overview</B></FONT></A> </TD>
<TD BGCOLOR="#FFFFFF" CLASS="NavBarCell1Rev"> <FONT CLASS="NavBarFont1Rev"><B>Package</B></FONT> </TD>
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <FONT CLASS="NavBarFont1">Class</FONT> </TD>
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <A HREF="package-use.html"><FONT CLASS="NavBarFont1"><B>Use</B></FONT></A> </TD>
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <A HREF="package-tree.html"><FONT CLASS="NavBarFont1"><B>Tree</B></FONT></A> </TD>
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <A HREF="../../../../deprecated-list.html"><FONT CLASS="NavBarFont1"><B>Deprecated</B></FONT></A> </TD>
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <A HREF="../../../../index-all.html"><FONT CLASS="NavBarFont1"><B>Index</B></FONT></A> </TD>
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <A HREF="../../../../help-doc.html"><FONT CLASS="NavBarFont1"><B>Help</B></FONT></A> </TD>
</TR>
</TABLE>
</TD>
<TD ALIGN="right" VALIGN="top" ROWSPAN=3><EM>
</EM>
</TD>
</TR>
<TR>
<TD BGCOLOR="white" CLASS="NavBarCell2"><FONT SIZE="-2">
<A HREF="../../../../org/apache/struts/taglib/tiles/util/package-summary.html"><B>PREV PACKAGE</B></A>
<A HREF="../../../../org/apache/struts/tiles/actions/package-summary.html"><B>NEXT PACKAGE</B></A></FONT></TD>
<TD BGCOLOR="white" CLASS="NavBarCell2"><FONT SIZE="-2">
<A HREF="../../../../index.html" TARGET="_top"><B>FRAMES</B></A>
<A HREF="package-summary.html" TARGET="_top"><B>NO FRAMES</B></A></FONT></TD>
</TR>
</TABLE>
<!-- =========== END OF NAVBAR =========== -->
<HR>
Copyright ⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -