You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by jk...@apache.org on 2006/10/15 08:09:02 UTC

svn commit: r464140 - /tapestry/tapestry4/trunk/src/site/xdoc/usersguide/

Author: jkuhnert
Date: Sat Oct 14 23:09:01 2006
New Revision: 464140

URL: http://svn.apache.org/viewvc?view=rev&rev=464140
Log:
Fixed some broken links.

Modified:
    tapestry/tapestry4/trunk/src/site/xdoc/usersguide/bindings.xml
    tapestry/tapestry4/trunk/src/site/xdoc/usersguide/components.xml
    tapestry/tapestry4/trunk/src/site/xdoc/usersguide/configuration.xml
    tapestry/tapestry4/trunk/src/site/xdoc/usersguide/friendly-urls.xml
    tapestry/tapestry4/trunk/src/site/xdoc/usersguide/injection.xml
    tapestry/tapestry4/trunk/src/site/xdoc/usersguide/listenermethods.xml
    tapestry/tapestry4/trunk/src/site/xdoc/usersguide/localization.xml
    tapestry/tapestry4/trunk/src/site/xdoc/usersguide/page-class.xml
    tapestry/tapestry4/trunk/src/site/xdoc/usersguide/script.xml
    tapestry/tapestry4/trunk/src/site/xdoc/usersguide/spec.xml
    tapestry/tapestry4/trunk/src/site/xdoc/usersguide/state.xml
    tapestry/tapestry4/trunk/src/site/xdoc/usersguide/template.xml
    tapestry/tapestry4/trunk/src/site/xdoc/usersguide/upgrade.xml

Modified: tapestry/tapestry4/trunk/src/site/xdoc/usersguide/bindings.xml
URL: http://svn.apache.org/viewvc/tapestry/tapestry4/trunk/src/site/xdoc/usersguide/bindings.xml?view=diff&rev=464140&r1=464139&r2=464140
==============================================================================
--- tapestry/tapestry4/trunk/src/site/xdoc/usersguide/bindings.xml (original)
+++ tapestry/tapestry4/trunk/src/site/xdoc/usersguide/bindings.xml Sat Oct 14 23:09:01 2006
@@ -141,23 +141,6 @@
                 <td>translator:number,pattern=#</td>
                 <td />
             </tr>
-
-            <tr>
-                <td>validator</td>
-                <td>
-                    Initializer used to obtain and configure an
-                    <a
-                        href="../tapestry-framework/apidocs/org/apache/tapestry/valid/IValidator.html">
-                        IValidator
-                    </a>
-                    instance (used with
-                    <a href="site:ValidField">ValidField</a>
-                    ).
-                </td>
-                <td>validator:string,required,minimumLength=5</td>
-                <td />
-            </tr>
-
             <tr>
                 <td>validators</td>
                 <td>
@@ -167,7 +150,7 @@
                         Validator
                     </a>
                     instances (used with
-                    <a href="site:TextField">TextField</a>
+                    <a href="../components/form/textfield.html">TextField</a>
                     and others).
                 </td>
                 <td>validators:email,required,minLength=10</td>

Modified: tapestry/tapestry4/trunk/src/site/xdoc/usersguide/components.xml
URL: http://svn.apache.org/viewvc/tapestry/tapestry4/trunk/src/site/xdoc/usersguide/components.xml?view=diff&rev=464140&r1=464139&r2=464140
==============================================================================
--- tapestry/tapestry4/trunk/src/site/xdoc/usersguide/components.xml (original)
+++ tapestry/tapestry4/trunk/src/site/xdoc/usersguide/components.xml Sat Oct 14 23:09:01 2006
@@ -288,12 +288,12 @@
                     is used to render
                     <em>this</em>
                     component's body. A component doesn't have to render its body; the standard
-                    <a href="site:Image">Image</a>
+                    <a href="../components/general/image.html">Image</a>
                     component doesn't render its body (and its component specification indicates
                     that it discards its body). The
-                    <a href="site:Conditional">Conditional</a>
+                    <a href="../components/general/if.html">If</a>
                     component decides whether or not to render its body, and the
-                    <a href="site:Foreach">Foreach</a>
+                    <a href="../components/general/for.html">For</a>
                     component may render its body multiple times.
                 </p>
 
@@ -366,9 +366,9 @@
                     The vast majority of components simply read their parameters. Updating
                     parameters is more rare; the most common components that update their parameters
                     are form element components such as
-                    <a href="site:TextField">TextField</a>
+                    <a href="../components/form/textfield.html">TextField</a>
                     or
-                    <a href="site:Checkbox">Checkbox</a>
+                    <a href="../components/form/checkbox.html">Checkbox</a>
                     .
                 </p>
 
@@ -385,10 +385,10 @@
                     Using
                     <a href="http://www.ognl.org">OGNL</a>
                     , the
-                    <a href="site:TextField">TextField</a>
+                    <a href="../components/form/textfield.html">TextField</a>
                     component's value parameter is bound to the LineItem's quantity property, using
                     the OGNL expression lineItem.quantity, and the
-                    <a href="site:Insert">Insert</a>
+                    <a href="../components/general/insert.html">Insert</a>
                     component's value parameter is bound to the Product's name property using the
                     OGNL expression lineItem.product.name.
                 </p>
@@ -755,7 +755,7 @@
                             IAsset
                         </a>
                         and treated identically by components (such as
-                        <a href="site:Image">Image</a>
+                        <a href="../components/general/image.html">Image</a>
                         ). As in this example, relative paths are allowed: they are interpreted
                         relative to the specification (page or component) they appear in.
                     </p>
@@ -862,9 +862,9 @@
                         the framework. This is frequently used to change the look and feel of the
                         default StateSession or Exception page. In theory, it is even possible to
                         override fundamental components such as
-                        <a href="site:Insert">Insert</a>
+                        <a href="../components/general/insert.html">Insert</a>
                         or
-                        <a href="site:Foreach">Foreach</a>
+                        <a href="../components/general/for.html">For</a>
                         !
                     </p>
 
@@ -881,9 +881,9 @@
                     <p>
                         You rarely need to be concerned with namespaces, however. The rare exception
                         is when a page from a library wishes to make use of the
-                        <a href="site:PageLink">PageLink</a>
+                        <a href="../components/link/pagelink.html">PageLink</a>
                         or
-                        <a href="site:ExternalLink">ExternalLink</a>
+                        <a href="../components/link/externallink.html">ExternalLink</a>
                         components to create a link to
                         <em>another page</em>
                         within the same namespace. This is accomplished (in the source page's HTML

Modified: tapestry/tapestry4/trunk/src/site/xdoc/usersguide/configuration.xml
URL: http://svn.apache.org/viewvc/tapestry/tapestry4/trunk/src/site/xdoc/usersguide/configuration.xml?view=diff&rev=464140&r1=464139&r2=464140
==============================================================================
--- tapestry/tapestry4/trunk/src/site/xdoc/usersguide/configuration.xml (original)
+++ tapestry/tapestry4/trunk/src/site/xdoc/usersguide/configuration.xml Sat Oct 14 23:09:01 2006
@@ -877,7 +877,7 @@
                         Specifies an implementation of ognl.TypeConverter to be used for expression
                         bindings. See OGNL's
                         <a
-                            href="http://www.ognl.org/2.6.3/Documentation/html/typeConversion.html">
+                            href="http://www.ognl.org/2.6.9/Documentation/html/DeveloperGuide/typeConversion.html">
                             Type Converter documentation
                         </a>
                         for further information on implementing a custom type converter.

Modified: tapestry/tapestry4/trunk/src/site/xdoc/usersguide/friendly-urls.xml
URL: http://svn.apache.org/viewvc/tapestry/tapestry4/trunk/src/site/xdoc/usersguide/friendly-urls.xml?view=diff&rev=464140&r1=464139&r2=464140
==============================================================================
--- tapestry/tapestry4/trunk/src/site/xdoc/usersguide/friendly-urls.xml (original)
+++ tapestry/tapestry4/trunk/src/site/xdoc/usersguide/friendly-urls.xml Sat Oct 14 23:09:01 2006
@@ -1,4 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE document PUBLIC "//xdoc/" "http://maven.apache.org/dtd/xdoc_1_0.dtd">
 <!-- 
     Copyright 2005 The Apache Software Foundation
     
@@ -62,15 +63,16 @@
                 was required).
             </p>
 
-            <p>
+            <span class="warn">
                 <strong>Warning:</strong>
-                <br />
+                <p>
                 For security purposes, enabling friendly URLs implies that pages are no longer
                 accessible via their ugly URL counterpart. This is not the case. If a malevolent
                 user can either guess - or via cookies identify - your servlet path, they can
                 construct an ugly URL to a resource that is protected via security and gain access
                 to the protected resource.
-            </p>
+                </p>
+            </span>
             <p>Friendly URLs are divided into two concerns:</p>
 
             <ul>
@@ -97,7 +99,7 @@
                 extension to the URL.
             </p>
 
-            <section name="Understanding Tapestry URLs">
+            <subsection name="Understanding Tapestry URLs">
 
 
                 <p>
@@ -113,16 +115,17 @@
                     query parameter is used to select an engine service by name. A number of
                     services are provided with the framework, the most common of which are:
                 </p>
-
+                
+                
                 <dl>
                     <dt>page</dt>
                     <dd>Activates and renders a specific page.</dd>
                     <dt>direct</dt>
                     <dd>
                         Used with the
-                        <a href="site:DirectLink">DirectLink</a>
+                        <a href="../components/link/directlink.html">DirectLink</a>
                         and
-                        <a href="site:Form">Form</a>
+                        <a href="../components/form/form.html">Form</a>
                         components.
                     </dd>
                     <dt>home</dt>
@@ -153,7 +156,7 @@
                     </dt>
                     <dd>
                         Stores listener parameters passed in the URL (used by
-                        <a href="site:DirectLink">DirectLink</a>
+                        <a href="../components/link/directlink.html">DirectLink</a>
                         and passed into
                         <a href="listenermethods.html">listener method</a>
                         s, the "sp" is a holdover from 3.0).
@@ -168,9 +171,9 @@
                     . Yep, that's UGLY.
                 </p>
 
-            </section>
+            </subsection>
 
-            <section name="Enabling Friendly URLs">
+            <subsection name="Enabling Friendly URLs">
 
 
                 <p>
@@ -180,7 +183,7 @@
                     </a>
                     . Enabling friendly URLs requires adding more configuration to web.xml, and to
                     your
-                    <a href="site:hivemind">HiveMind module deployment descriptor</a>
+                    <a href="hivemind.html">HiveMind module deployment descriptor</a>
                     .
                 </p>
 
@@ -431,7 +434,7 @@
                         From the Virtual Library example, a custom encoder implementation is used as
                         a special way to reference the ViewBook and ViewPerson pages using the
                         external service (see the
-                        <a href="site:ExternalLink">ExternalLink</a>
+                        <a href="../components/link/externallink.html">ExternalLink</a>
                         component for more information about using this engine service). The end
                         result is that the URLs for these two pages look like
                         <code>/vlib/book/2096</code>
@@ -560,7 +563,7 @@
                     start with a slash.
                 </p>
 
-            </section>
+            </subsection>
 
         </section>
     </body>

Modified: tapestry/tapestry4/trunk/src/site/xdoc/usersguide/injection.xml
URL: http://svn.apache.org/viewvc/tapestry/tapestry4/trunk/src/site/xdoc/usersguide/injection.xml?view=diff&rev=464140&r1=464139&r2=464140
==============================================================================
--- tapestry/tapestry4/trunk/src/site/xdoc/usersguide/injection.xml (original)
+++ tapestry/tapestry4/trunk/src/site/xdoc/usersguide/injection.xml Sat Oct 14 23:09:01 2006
@@ -70,7 +70,7 @@
             </p>
 
 
-            <section name="meta injection">
+            <subsection name="meta injection">
 
 
                 <p>
@@ -118,9 +118,9 @@
   
 </source>
 
-            </section><!-- injection.meta -->
+            </subsection><!-- injection.meta -->
 
-            <section name="object injection">
+            <subsection name="object injection">
 
 
                 <p>
@@ -134,9 +134,9 @@
 
                 </p>
 
-            </section><!-- injection.object -->
+            </subsection><!-- injection.object -->
 
-            <section name="page injection">
+            <subsection name="page injection">
 
 
                 <p>
@@ -186,9 +186,9 @@
                     activated to render the response.
                 </p>
 
-            </section><!-- injection.page -->
+            </subsection><!-- injection.page -->
 
-            <section name="script injection">
+            <subsection name="script injection">
 
 
                 <p>
@@ -227,9 +227,9 @@
   getScript().execute(cycle, pageRenderSupport, _symbols);
 </source>
 
-            </section><!-- injection.script -->
+            </subsection><!-- injection.script -->
 
-            <section name="state injection">
+            <subsection name="state injection">
 
 
                 <p>
@@ -239,9 +239,9 @@
                     many pages).
                 </p>
 
-            </section>
+            </subsection>
 
-            <section name="state-flag injection">
+            <subsection name="state-flag injection">
 
 
                 <p>
@@ -288,7 +288,7 @@
   }
 }
 </source>
-            </section><!-- injection.state-flag -->
+            </subsection><!-- injection.state-flag -->
         </section>
     </body>
 </document>

Modified: tapestry/tapestry4/trunk/src/site/xdoc/usersguide/listenermethods.xml
URL: http://svn.apache.org/viewvc/tapestry/tapestry4/trunk/src/site/xdoc/usersguide/listenermethods.xml?view=diff&rev=464140&r1=464139&r2=464140
==============================================================================
--- tapestry/tapestry4/trunk/src/site/xdoc/usersguide/listenermethods.xml (original)
+++ tapestry/tapestry4/trunk/src/site/xdoc/usersguide/listenermethods.xml Sat Oct 14 23:09:01 2006
@@ -30,9 +30,9 @@
             Listener methods are a kind of call back; they are triggered when a form is submitted or
             a link is clicked. The listener methods exist within your page and component classes.
             Components such as
-            <a href="site:DirectLink">DirectLink</a>
+            <a href="../components/link/directlink.html">DirectLink</a>
             and
-            <a href="site:Form">Form</a>
+            <a href="../components/form/form.html">Form</a>
             take a listener parameter, and you can use a listener:
             <a href="bindings.html">binding reference</a>
             to use a listener method in your class as the listener.
@@ -120,7 +120,7 @@
 
             <p>
                 When using the
-                <a href="site:DirectLink">DirectLink</a>
+                <a href="../components/link/directlink.html">DirectLink</a>
                 component, you may specify additional
                 <em>listener parameters</em>
                 . The listener parameters are encoded into the URL and will be available in a later

Modified: tapestry/tapestry4/trunk/src/site/xdoc/usersguide/localization.xml
URL: http://svn.apache.org/viewvc/tapestry/tapestry4/trunk/src/site/xdoc/usersguide/localization.xml?view=diff&rev=464140&r1=464139&r2=464140
==============================================================================
--- tapestry/tapestry4/trunk/src/site/xdoc/usersguide/localization.xml (original)
+++ tapestry/tapestry4/trunk/src/site/xdoc/usersguide/localization.xml Sat Oct 14 23:09:01 2006
@@ -29,7 +29,7 @@
                 color schemes.
             </p>
             <p>Localization support in Tapestry is likewise pervasive.</p>
-            <section name="Component Message Catalogs">
+            <subsection name="Component Message Catalogs">
 
                 <p>
                     The most fundamental aspect of localization in Tapestry are component message
@@ -163,8 +163,8 @@
                     </p>
 
                 </subsection>
-            </section>
-            <section name="Missing keys">
+            </subsection>
+            <subsection name="Missing keys">
 
 
                 <p>
@@ -177,8 +177,8 @@
                     completely subverting your application.
                 </p>
 
-            </section><!-- localization.missing-keys -->
-            <section name="Namespace message catalogs">
+            </subsection><!-- localization.missing-keys -->
+            <subsection name="Namespace message catalogs">
 
 
                 <p>
@@ -209,9 +209,9 @@
                     still have properties, just as if the application specification existed.
                 </p>
 
-            </section><!-- localization.namespace -->
+            </subsection><!-- localization.namespace -->
             <!-- localization.component-catalog -->
-            <section name="Template text localization">
+            <subsection name="Template text localization">
 
                 <p>
                     As described in
@@ -222,9 +222,9 @@
                     tag.
                 </p>
 
-            </section>
+            </subsection>
 
-            <section name="Localized templates">
+            <subsection name="Localized templates">
 
 
                 <p>
@@ -253,9 +253,9 @@
                     components, when using localized templates ... it reduces duplication in the
                     templates.
                 </p>
-            </section>
+            </subsection>
 
-            <section name="Template encoding">
+            <subsection name="Template encoding">
 
 
                 <p>
@@ -282,9 +282,9 @@
                         </a>
                     </li>
                 </ul>
-            </section>
+            </subsection>
 
-            <section name="Using the message: binding prefix">
+            <subsection name="Using the message: binding prefix">
 
 
                 <p>
@@ -294,14 +294,14 @@
                 </p>
 
                 <source xml:space="preserve">
-&lt;html jwcid="@<a href="site:Shell">Shell</a>" title="message:page-title"&gt;
+&lt;html jwcid="@<a href="../components/general/shell.html">Shell</a>" title="message:page-title"&gt;
  . . .
 &lt;/html&gt;
 </source>
 
-            </section>
+            </subsection>
 
-            <section name="Localization of Assets">
+            <subsection name="Localization of Assets">
 
 
                 <p>
@@ -309,9 +309,9 @@
                     search for a locale-specific match (this is very similar to how localized
                     templates work).
                 </p>
-            </section><!-- localization.assets -->
+            </subsection><!-- localization.assets -->
 
-            <section name="Formatting messages">
+            <subsection name="Formatting messages">
 
 
                 <p>
@@ -346,7 +346,7 @@
                 <p>It is common to format messages using OGNL expessions, i.e.:</p>
 
                 <source xml:space="preserve">
-&lt;span jwcid="@<a href="site:Insert">Insert</a>" value="ognl:messages.format('billing-info', amountDue)"/&gt;
+&lt;span jwcid="@<a href="../components/general/insert.html">Insert</a>" value="ognl:messages.format('billing-info', amountDue)"/&gt;
 </source>
 
                 <p>
@@ -354,9 +354,9 @@
                     to the message format retrieved from the message catalog as key 'billing-info'.
                 </p>
 
-            </section>
+            </subsection>
 
-            <section name="Changing the locale">
+            <subsection name="Changing the locale">
 
 
                 <p>
@@ -389,9 +389,9 @@
                 </p>
 
 
-            </section>
+            </subsection>
 
-            <section name="Engine locale vs. page locale">
+            <subsection name="Engine locale vs. page locale">
 
 
                 <p>
@@ -432,9 +432,9 @@
                     </p>
                 </span>
 
-            </section>
+            </subsection>
 
-            <section name="Limiting accepted locales">
+            <subsection name="Limiting accepted locales">
 
 
                 <p>
@@ -474,7 +474,7 @@
                     users would be matched to the "en" locale.
                 </p>
 
-            </section>
+            </subsection>
         </section>
     </body>
 </document>

Modified: tapestry/tapestry4/trunk/src/site/xdoc/usersguide/page-class.xml
URL: http://svn.apache.org/viewvc/tapestry/tapestry4/trunk/src/site/xdoc/usersguide/page-class.xml?view=diff&rev=464140&r1=464139&r2=464140
==============================================================================
--- tapestry/tapestry4/trunk/src/site/xdoc/usersguide/page-class.xml (original)
+++ tapestry/tapestry4/trunk/src/site/xdoc/usersguide/page-class.xml Sat Oct 14 23:09:01 2006
@@ -111,7 +111,7 @@
                 searched for the list of packages, and later, for the default page class name.
             </p>
 
-            <section name="Component Classes">
+            <subsection name="Component Classes">
 
 
                 <p>
@@ -151,7 +151,7 @@
                         configuration point.
                     </p>
                 </span>
-            </section>
+            </subsection>
             
         </section>
         

Modified: tapestry/tapestry4/trunk/src/site/xdoc/usersguide/script.xml
URL: http://svn.apache.org/viewvc/tapestry/tapestry4/trunk/src/site/xdoc/usersguide/script.xml?view=diff&rev=464140&r1=464139&r2=464140
==============================================================================
--- tapestry/tapestry4/trunk/src/site/xdoc/usersguide/script.xml (original)
+++ tapestry/tapestry4/trunk/src/site/xdoc/usersguide/script.xml Sat Oct 14 23:09:01 2006
@@ -59,7 +59,7 @@
                     IScriptProcessor
                 </a>
                 instance; this is usually provided by the
-                <a href="site:Body">Body</a>
+                <a href="../components/general/body.html">Body</a>
                 component. The script processor is responsible for managing the buffers of
                 JavaScript, and assists with generating unique ids for client-side variables and
                 functions.
@@ -85,7 +85,7 @@
                 .
             </p>
 
-            <section name="DOCTYPE">
+            <subsection name="DOCTYPE">
 
 
                 <p>The DOCTYPE for a script template specification is:</p>
@@ -94,9 +94,9 @@
 &lt;!DOCTYPE script PUBLIC
   "-//Apache Software Foundation//Tapestry Script Specification 3.0//EN"
   "http://jakarta.apache.org/tapestry/dtd/Script_3_0.dtd"&gt;</source>
-            </section><!-- DOCTYPE -->
+            </subsection><!-- DOCTYPE -->
 
-            <section name="&lt;body&gt; element">
+            <subsection name="&lt;body&gt; element">
 
 
                 <p>
@@ -114,9 +114,9 @@
                 <source xml:space="preserve">(<em>text</em> | <a href="#script.foreach">&lt;foreach&gt;</a> | <a
                         href="#script.if">&lt;if&gt;</a> | <a href="#script.if-not">&lt;if-not&gt;</a> | <a
                         href="#script.unique">&lt;unique&gt;</a>)*</source>
-            </section>
+            </subsection>
 
-            <section name="&lt;foreach&gt; element">
+            <subsection name="&lt;foreach&gt; element">
 
 
                 <p>
@@ -174,10 +174,10 @@
                 <source xml:space="preserve">(<em>text</em> | <a href="#script.foreach">&lt;foreach&gt;</a> | <a
                         href="#script.if">&lt;if&gt;</a> | <a href="#script.if-not">&lt;if-not&gt;</a> | <a
                         href="#script.unique">&lt;unique&gt;</a>)*</source>
-            </section>
+            </subsection>
 
 
-            <section name="&lt;if&gt; element">
+            <subsection name="&lt;if&gt; element">
 
 
                 <p>
@@ -221,9 +221,9 @@
                         href="#script.if">&lt;if&gt;</a> | <a href="#script.if-not">&lt;if-not&gt;</a> | <a
                         href="#script.unique">&lt;unique&gt;</a>)*</source>
 
-            </section>
+            </subsection>
 
-            <section name="&lt;if-not&gt; element">
+            <subsection name="&lt;if-not&gt; element">
 
 
                 <p>
@@ -234,11 +234,11 @@
                     <strong>false</strong>
                     .
                 </p>
-            </section>
+            </subsection>
 
 
 
-            <section name="&lt;include-script&gt; element">
+            <subsection name="&lt;include-script&gt; element">
 
 
                 <p>
@@ -279,8 +279,8 @@
                     </tr>
                 </table>
 
-            </section>
-            <section name="&lt;initialization&gt; element">
+            </subsection>
+            <subsection name="&lt;initialization&gt; element">
 
 
                 <p>
@@ -299,9 +299,9 @@
                 <source xml:space="preserve">(<em>text</em> | <a href="#script.foreach">&lt;foreach&gt;</a> | <a
                         href="#script.if">&lt;if&gt;</a> | <a href="#script.if-not">&lt;if-not&gt;</a> | <a
                         href="#script.unique">&lt;unique&gt;</a>)*</source>
-            </section>
+            </subsection>
 
-            <section name="&lt;input-symbol&gt; element">
+            <subsection name="&lt;input-symbol&gt; element">
 
 
                 <p>
@@ -356,9 +356,9 @@
                     </tr>
                 </table>
 
-            </section>
+            </subsection>
 
-            <section name="&lt;let&gt; element">
+            <subsection name="&lt;let&gt; element">
 
 
                 <p>
@@ -414,9 +414,9 @@
                         href="#script.unique">&lt;unique&gt;</a>)*</source>
 
 
-            </section>
+            </subsection>
 
-            <section name="&lt;script&gt; element">
+            <subsection name="&lt;script&gt; element">
 
 
                 <p>
@@ -435,10 +435,10 @@
                         href="#script.body">&lt;body&gt;</a>?, <a href="#script.initialization">&lt;initialization&gt;</a>?)                  
             </source>
 
-            </section><!-- script -->
+            </subsection><!-- script -->
 
 
-            <section name="&lt;set&gt; element">
+            <subsection name="&lt;set&gt; element">
 
 
                 <p>
@@ -483,9 +483,9 @@
                     </tr>
                 </table>
 
-            </section><!-- script.set -->
+            </subsection><!-- script.set -->
 
-            <section name="&lt;unique&gt; element">
+            <subsection name="&lt;unique&gt; element">
 
 
                 <p>
@@ -505,7 +505,7 @@
                         href="#script.if">&lt;if&gt;</a> | <a href="#script.if-not">&lt;if-not&gt;</a> | <a
                         href="#script.unique">&lt;unique&gt;</a>)*</source>
 
-            </section>
+            </subsection>
 
         </section>
 

Modified: tapestry/tapestry4/trunk/src/site/xdoc/usersguide/spec.xml
URL: http://svn.apache.org/viewvc/tapestry/tapestry4/trunk/src/site/xdoc/usersguide/spec.xml?view=diff&rev=464140&r1=464139&r2=464140
==============================================================================
--- tapestry/tapestry4/trunk/src/site/xdoc/usersguide/spec.xml (original)
+++ tapestry/tapestry4/trunk/src/site/xdoc/usersguide/spec.xml Sat Oct 14 23:09:01 2006
@@ -870,7 +870,7 @@
                             <p>
                                 If true, then any body for this component, from its containing page
                                 or component's template, is retained and may be rendered using a
-                                <a href="site:RenderBody">RenderBody</a>
+                                <a href="../components/general/renderbody.html">RenderBody</a>
                                 component.
                             </p>
                             <p>

Modified: tapestry/tapestry4/trunk/src/site/xdoc/usersguide/state.xml
URL: http://svn.apache.org/viewvc/tapestry/tapestry4/trunk/src/site/xdoc/usersguide/state.xml?view=diff&rev=464140&r1=464139&r2=464140
==============================================================================
--- tapestry/tapestry4/trunk/src/site/xdoc/usersguide/state.xml (original)
+++ tapestry/tapestry4/trunk/src/site/xdoc/usersguide/state.xml Sat Oct 14 23:09:01 2006
@@ -495,7 +495,7 @@
 
                     <p>
                         To create a new ASO, you must update your
-                        <a href="site:hivemind">HiveMind module deployment descriptor</a>
+                        <a href="hivemind.html">HiveMind module deployment descriptor</a>
                         and add a contribution to the
                         <a
                             href="../tapestry/hivedocs/config/tapestry.state.ApplicationObjects.html">
@@ -692,7 +692,7 @@
                     <code>state:</code>
                     <a href="bindings.html">binding reference</a>
                     combined with the
-                    <a href="site:If">If</a>
+                    <a href="../components/general/if.html">If</a>
                     component makes it easy for you to skip portions of a page if a particular ASO
                     does not already exist; this allows you to avoid accidentally forcing its
                     creation on first reference.

Modified: tapestry/tapestry4/trunk/src/site/xdoc/usersguide/template.xml
URL: http://svn.apache.org/viewvc/tapestry/tapestry4/trunk/src/site/xdoc/usersguide/template.xml?view=diff&rev=464140&r1=464139&r2=464140
==============================================================================
--- tapestry/tapestry4/trunk/src/site/xdoc/usersguide/template.xml (original)
+++ tapestry/tapestry4/trunk/src/site/xdoc/usersguide/template.xml Sat Oct 14 23:09:01 2006
@@ -171,7 +171,7 @@
                     The second span is an
                     <em>implicit component</em>
                     ; the type of the component is
-                    <a href="site:Insert">Insert</a>
+                    <a href="../components/general/insert.html">Insert</a>
                     . The value parameter is bound to the
                     <a href="http://www.ognl.org">OGNL</a>
                     expression
@@ -255,7 +255,7 @@
                         In most cases, a component will make use of its body; it simply controls if,
                         when and how often its body is rendered (when rendering the HTML response
                         sent to the client). Other components, such as
-                        <a href="site:Insert">Insert</a>
+                        <a href="../components/general/insert.html">Insert</a>
                         , have no use for their bodies, which they discard. Each component declares
                         in its own specification (the allow-body attribute of the
                         <a href="spec.html#spec.component-specification">
@@ -266,10 +266,10 @@
 
                     <p>
                         In the previous example, the
-                        <a href="site:Insert">Insert</a>
+                        <a href="../components/general/insert.html">Insert</a>
                         component had a body, the text "Joe User". This supports WYSIWYG preview;
                         the text will be displayed when previewing. Since the
-                        <a href="site:Insert">Insert</a>
+                        <a href="../components/general/insert.html">Insert</a>
                         component discards its body, this text will not be used at runtime, instead
                         the OGNL expression
                         <code>user.name</code>
@@ -280,7 +280,7 @@
                         <strong>Warning:</strong>
                         <p>
                             If you put a component inside the body of an
-                            <a href="site:Insert">Insert</a>
+                            <a href="../components/general/insert.html">Insert</a>
                             (or any other component that discards its body), then Tapestry will
                             throw an exception. You aren't allowed to create a component simply to
                             discard it.
@@ -300,7 +300,7 @@
                         component's type; this component would have an id of
                         <code>$Insert</code>
                         ; other
-                        <a href="site:Insert">Insert</a>
+                        <a href="../components/general/insert.html">Insert</a>
                         components would have ids
                         <code>$Insert$0</code>
                         ,
@@ -534,7 +534,7 @@
                     <p>
                         Another conflict can occur when the HTML template specified an attribute
                         that the component needs to render itself. For example, the
-                        <a href="site:DirectLink">DirectLink</a>
+                        <a href="../components/link/directlink.html">DirectLink</a>
                         component generates a
                         <code>&lt;a&gt;</code>
                         tag, and needs to control the href attribute. However, for preview purposes,
@@ -548,7 +548,7 @@
                     <p>
                         This creates a conflict: will the template href (the literal string "#") be
                         used, or the dynamically generated URL produced by the
-                        <a href="site:DirectLink">DirectLink</a>
+                        <a href="../components/link/directlink.html">DirectLink</a>
                         component, or both? The answer is: the component wins. The href attribute in
                         the template is ignored.
                     </p>
@@ -628,7 +628,7 @@
 
                     <p>
                         This is not an
-                        <a href="site:Insert">Insert</a>
+                        <a href="../components/general/insert.html">Insert</a>
                         component, but behaves in a similar way. The tag used
                         <em>must be</em>
                         &lt;span&gt;. You do not use the
@@ -722,7 +722,7 @@
                         people, perhaps from some kind of database. When this page renders, the
                         <code>loop</code>
                         component (presumably a
-                        <a href="site:Foreach">Foreach</a>
+                        <a href="../components/general/for.html">Foreach</a>
                         , such details being in the page's specification) will render its body zero
                         or more times. So we might see rows for "Frank Miller", "Alan Moore" and so
                         forth (depending on the content of the database). However, every listing

Modified: tapestry/tapestry4/trunk/src/site/xdoc/usersguide/upgrade.xml
URL: http://svn.apache.org/viewvc/tapestry/tapestry4/trunk/src/site/xdoc/usersguide/upgrade.xml?view=diff&rev=464140&r1=464139&r2=464140
==============================================================================
--- tapestry/tapestry4/trunk/src/site/xdoc/usersguide/upgrade.xml (original)
+++ tapestry/tapestry4/trunk/src/site/xdoc/usersguide/upgrade.xml Sat Oct 14 23:09:01 2006
@@ -475,16 +475,12 @@
             </section>
 
             <section name="Changes to Components">
-
-
                 <subsection name="Image and Rollover">
-
-
                     <p>
                         The border parameter of the
-                        <a href="site:Image">Image</a>
+                        <a href="../components/general/image.html">Image</a>
                         and
-                        <a href="site:Rollover">Rollover</a>
+                        <a href="../components/link/rollover.html">Rollover</a>
                         components has been removed, for XHTML compliance. You may still specify a
                         value for border as an informal parameter ... or better yet, handle this
                         using CSS.