You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by bu...@apache.org on 2012/05/22 10:25:36 UTC
svn commit: r818658 [19/23] - in /websites/staging/sling/trunk/content: ./
tutorials-how-tos/
Modified: websites/staging/sling/trunk/content/servlets.html
==============================================================================
--- websites/staging/sling/trunk/content/servlets.html (original)
+++ websites/staging/sling/trunk/content/servlets.html Tue May 22 08:25:32 2012
@@ -82,86 +82,58 @@
<a href="/">Home</a>
</div>
<h1>Servlets</h1>
- <p><a name="Servlets-ServletsandScripts"></a></p>
-<h1 id="servlets-and-scripts">Servlets and Scripts</h1>
-<p>Servlets can be registered as OSGi services. The following service
-reference properties are defined for Servlets defined as OSGi services of
-type <em>javax.servlet.Servlet</em>:</p>
+ <h1 id="servlets-and-scripts">Servlets and Scripts</h1>
+<p>Servlets can be registered as OSGi services. The following service reference properties are defined for Servlets defined as OSGi services of type <code>javax.servlet.Servlet</code>:</p>
<table>
-<tr><th> Name </th><th> Description </th></tr>
-<tr><td> *sling.servlet.paths* </td><td> A list of absolute paths under which the
-servlet is accessible as a Resource. The property value must either be a
-single String, an array of Strings or a Vector of Strings. </td></tr>
-<tr><td> *sling.servlet.resourceTypes* </td><td> The resource type(s) supported by the
-servlet. The property value must either be a single String, an array of
-Strings or a Vector of Strings. This property is ignored if the
-*sling.servlet.paths* property is set. </td></tr>
-<tr><td> *sling.servlet.selectors* </td><td> The request URL selectors supported by the
-servlet. The selectors must be configured as they would be specified in the
-URL that is as a list of dot-separated strings such as <em>print.a4</em>.
-The property value must either be a single String, an array of Strings or a
-Vector of Strings. This property is ignored if the *sling.servlet.paths*
-property is set. </td></tr>
-<tr><td> *sling.servlet.extensions* </td><td> The request URL extensions supported by
-the servlet for requests. The property value must either be a single
-String, an array of Strings or a Vector of Strings. This property is
-ignored if the *sling.servlet.paths* property is set. </td></tr>
-<tr><td> *sling.servlet.methods* </td><td> The request methods supported by the servlet.
-The property value must either be a single String, an array of Strings or a
-Vector of Strings. This property is ignored if the *sling.servlet.paths*
-property is set. If this property is missing, the value defaults to GET,
-regardless of which methods are actually implemented/handled by the
-servlet.</td></tr>
-<tr><td> *sling.servlet.prefix* </td><td> The prefix or numeric index to make relative
-paths absolute. If the value of this property is a number (int), it defines
-the index of the search path entries from the resource resolver to be used
-as the prefix. The defined search path is used as a prefix to mount this
-servlet. The number can be -1 which always points to the last search entry.
-If the specified value is higher than than the highest index of the search
-paths, the last entry is used. The index starts with 0. If the value of
-this property is a string and parseable as a number, the value is treated
-as if it would be a number. If the value of this property is a string
-starting with "/", this value is applied as a prefix, regardless of the
-configured search paths! If the value is anything else, it is ignored. If
-this property is not specified, it defaults to the default configuration of
-the sling servlet resolver. </td></tr>
+<thead>
+<tr>
+<th>Name</th>
+<th>Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td><code>sling.servlet.paths</code></td>
+<td>A list of absolute paths under which the servlet is accessible as a Resource. The property value must either be a single String, an array of Strings or a Vector of Strings.</td>
+</tr>
+<tr>
+<td>A servlet using this property might be ignored unless its path is included in the <em>Execution Paths</em> (<code>servletresolver.paths</code>) configuration setting of the <code>SlingServletResolver</code> service.</td>
+<td></td>
+</tr>
+<tr>
+<td>Creating a resource at the desired path, with a resource type that maps to a servlet, provides the same result in most cases while taking advantage of more Sling built-in features.</td>
+<td></td>
+</tr>
+<tr>
+<td><code>sling.servlet.resourceTypes</code></td>
+<td>The resource type(s) supported by the servlet. The property value must either be a single String, an array of Strings or a Vector of Strings. This property is ignored if the <code>sling.servlet.paths</code> property is set.</td>
+</tr>
+<tr>
+<td><code>sling.servlet.selectors</code></td>
+<td>The request URL selectors supported by the servlet. The selectors must be configured as they would be specified in the URL that is as a list of dot-separated strings such as <em>print.a4</em>. The property value must either be a single String, an array of Strings or a Vector of Strings. This property is ignored if the <code>sling.servlet.paths</code> property is set.</td>
+</tr>
+<tr>
+<td><code>sling.servlet.extensions</code></td>
+<td>The request URL extensions supported by the servlet for requests. The property value must either be a single String, an array of Strings or a Vector of Strings. This property is ignored if the <code>sling.servlet.paths</code> property is set.</td>
+</tr>
+<tr>
+<td><code>sling.servlet.methods</code></td>
+<td>The request methods supported by the servlet. The property value must either be a single String, an array of Strings or a Vector of Strings. This property is ignored if the <code>sling.servlet.paths</code> property is set. If this property is missing, the value defaults to GET, regardless of which methods are actually implemented/handled by the servlet.</td>
+</tr>
+<tr>
+<td><code>sling.servlet.prefix</code></td>
+<td>The prefix or numeric index to make relative paths absolute. If the value of this property is a number (int), it defines the index of the search path entries from the resource resolver to be used as the prefix. The defined search path is used as a prefix to mount this servlet. The number can be -1 which always points to the last search entry. If the specified value is higher than than the highest index of the search paths, the last entry is used. The index starts with 0. If the value of this property is a string and parseable as a number, the value is treated as if it would be a number. If the value of this property is a string starting with "/", this value is applied as a prefix, regardless of the configured search paths! If the value is anything else, it is ignored. If this property is not specified, it defaults to the default configuration of the sling servlet resolver.</td>
+</tr>
+</tbody>
</table>
-
-<p>A <em>SlingServletResolver</em> listens for <em>Servlet{</em>}services and - given
-the correct service registration properties - provides the servlets as
-resources in the (virtual) resource tree. Such servlets are provided as
-<em>ServletResource</em> instances which adapt to the <em>javax.servlet.Servlet</em>
-class.</p>
-<p>For a Servlet registered as an OSGi service to be used by the Sling Servlet
-Resolver, the either or both of the <em>sling.servlet.paths</em> or the
-<em>sling.servlet.resourceTypes</em> service reference properties must be set.
-If neither is set, the Servlet service is ignored.</p>
-<p>Each path to be used for registration - either from the
-<em>sling.servlet.paths</em> property or constructed from the other
-<em>sling.servlet.*</em> properties - must be absolute. Any relative path is
-made absolute by prefixing it with a root path. This prefix may be set with
-the <em>sling.servlet.prefix</em> service registration property. If this
-property is not set, the first entry in the <em>ResourceResolver</em> search
-path for the <em>ResourceResolver.getResource(String)</em> method is used as the
-prefix. If this entry cannot be derived, a simpe slash - <em>/</em> - is used
-as the prefix.</p>
-<p>If <em>sling.servlet.methods</em> is not specified, the servlet is only
-registered for handling GET requests. Make sure to list all methods you
-want to be handled by this servlet.</p>
-<p><a name="Servlets-Automatedtests"></a></p>
+<p>A <code>SlingServletResolver</code> listens for <code>Servlet{</code>}services and - given the correct service registration properties - provides the servlets as resources in the (virtual) resource tree. Such servlets are provided as <code>ServletResource</code> instances which adapt to the <code>javax.servlet.Servlet</code> class.</p>
+<p>For a Servlet registered as an OSGi service to be used by the Sling Servlet Resolver, the either or both of the <code>sling.servlet.paths</code> or the <code>sling.servlet.resourceTypes</code> service reference properties must be set. If neither is set, the Servlet service is ignored.</p>
+<p>Each path to be used for registration - either from the <code>sling.servlet.paths</code> property or constructed from the other <code>sling.servlet.\*</code> properties - must be absolute. Any relative path is made absolute by prefixing it with a root path. This prefix may be set with the <code>sling.servlet.prefix</code> service registration property. If this property is not set, the first entry in the <code>ResourceResolver</code> search path for the <code>ResourceResolver.getResource(String)</code> method is used as the prefix. If this entry cannot be derived, a simpe slash - <code>/</code> - is used as the prefix.</p>
+<p>If <code>sling.servlet.methods</code> is not specified, the servlet is only registered for handling GET requests. Make sure to list all methods you want to be handled by this servlet.</p>
<h3 id="automated-tests">Automated tests</h3>
-<p>The <a href="http://svn.apache.org/repos/asf/sling/trunk/launchpad/test-services/">launchpad/test-services</a>
- module contains test servlets that use various combinations of the above
-properties. </p>
-<p>The <a href="http://svn.apache.org/repos/asf/sling/trunk/launchpad/integration-tests/">launchpad/integration-tests</a>
- module contains a number of tests (like the [ExtensionServletTest|http://svn.apache.org/repos/asf/sling/trunk/launchpad/integration-tests/src/main/java/org/apache/sling/launchpad/webapp/integrationtest/servlets/resolution/ExtensionServletTest.java]
- for example) that verify the results.</p>
-<p>Such tests run as part of our continuous integration process, to
-demonstrate and verify the behavior of the various servlet registration
-mechanisms, in a way that's guaranteed to be in sync with the actual Sling
-core code. If you have an idea for additional tests, make sure to let us
-know!</p>
-<p><a name="Servlets-Example:RegistrationbyPath"></a></p>
+<p>The <a href="">launchpad/test-services</a> module contains test servlets that use various combinations of the above properties. </p>
+<p>The <a href="">launchpad/integration-tests</a> module contains a number of tests (like the [ExtensionServletTest|http://svn.apache.org/repos/asf/sling/trunk/launchpad/integration-tests/src/main/java/org/apache/sling/launchpad/webapp/integrationtest/servlets/resolution/ExtensionServletTest.java] for example) that verify the results.</p>
+<p>Such tests run as part of our continuous integration process, to demonstrate and verify the behavior of the various servlet registration mechanisms, in a way that's guaranteed to be in sync with the actual Sling core code. If you have an idea for additional tests, make sure to let us know!</p>
<h3 id="example-registration-by-path">Example: Registration by Path</h3>
<div class="codehilite"><pre><span class="n">sling</span><span class="o">.</span><span class="n">servlet</span><span class="o">.</span><span class="n">paths</span> <span class="o">=</span> <span class="o">\</span><span class="p">[</span> <span class="s">"/libs/sling/sample/html"</span><span class="p">,</span> <span class="s">"/libs/sling/sample/txt"</span> <span class="o">\</span><span class="p">]</span>
<span class="n">sling</span><span class="o">.</span><span class="n">servlet</span><span class="o">.</span><span class="n">resourceTypes</span> <span class="o">=</span> <span class="o">\</span><span class="p">[</span> <span class="s">"sling/unused"</span> <span class="o">\</span><span class="p">]</span>
@@ -170,16 +142,12 @@ know!</p>
</pre></div>
-<p>A Servlet service registered with these properties is registered under the
-following paths:</p>
+<p>A Servlet service registered with these properties is registered under the following paths:</p>
<ul>
-<li><em>/libs/sling/sample/html</em></li>
-<li><em>/libs/sling/sample/txt</em></li>
+<li><code>/libs/sling/sample/html</code></li>
+<li><code>/libs/sling/sample/txt</code></li>
</ul>
-<p>The registration properties <em>sling.servlet.resourceTypes</em>,
-<em>sling.servlet.selectors</em> and <em>sling.servlet.extensions</em> <em>are ignored</em>
-because the <em>sling.servlet.paths</em> property is set.</p>
-<p><a name="Servlets-Example:RegistrationbyResourceTypeetc."></a></p>
+<p>The registration properties <code>sling.servlet.resourceTypes</code>, <code>sling.servlet.selectors</code> and <code>sling.servlet.extensions</code> <em>are ignored</em> because the <code>sling.servlet.paths</code> property is set.</p>
<h3 id="example-registration-by-resource-type-etc">Example: Registration by Resource Type etc.</h3>
<div class="codehilite"><pre><span class="n">sling</span><span class="o">.</span><span class="n">servlet</span><span class="o">.</span><span class="n">resourceTypes</span> <span class="o">=</span> <span class="o">\</span><span class="p">[</span> <span class="s">"sling/unused"</span> <span class="o">\</span><span class="p">]</span>
<span class="n">sling</span><span class="o">.</span><span class="n">servlet</span><span class="o">.</span><span class="n">selectors</span> <span class="o">=</span> <span class="o">\</span><span class="p">[</span> <span class="s">"img"</span><span class="p">,</span> <span class="s">"tab"</span> <span class="o">\</span><span class="p">]</span>
@@ -187,72 +155,36 @@ because the <em>sling.servlet.paths</em>
</pre></div>
-<p>A Servlet service registered with these properties is registered under the
-following paths:</p>
+<p>A Servlet service registered with these properties is registered under the following paths:</p>
<ul>
-<li><em>{<em>}prefix</em>/sling/unused/img/html</em></li>
-<li><em>{<em>}prefix</em>/sling/unused/img/txt</em></li>
-<li><em>{<em>}prefix</em>/sling/unused/img/json</em></li>
-<li><em>{<em>}prefix</em>/sling/unused/tab/html</em></li>
-<li><em>{<em>}prefix</em>/sling/unused/tab/txt</em></li>
-<li><em>{<em>}prefix</em>/sling/unused/tab/json</em></li>
+<li><code>{*}prefix*/sling/unused/img/html</code></li>
+<li><code>{*}prefix*/sling/unused/img/txt</code></li>
+<li><code>{*}prefix*/sling/unused/img/json</code></li>
+<li><code>{*}prefix*/sling/unused/tab/html</code></li>
+<li><code>{*}prefix*/sling/unused/tab/txt</code></li>
+<li><code>{*}prefix*/sling/unused/tab/json</code></li>
</ul>
-<p>As explained the Servlet is registered for each permutation of the resource
-types, selectors and extension. See above For an explanation of how
-<em>{<em>}prefix{</em></em>} is defined.</p>
-<p><a name="Servlets-ScriptsareServlets"></a></p>
+<p>As explained the Servlet is registered for each permutation of the resource types, selectors and extension. See above For an explanation of how <code>{*}prefix{*</code>} is defined.</p>
<h2 id="scripts-are-servlets">Scripts are Servlets</h2>
-<p>The Sling API defines a <em>SlingScript</em> interface which is used to
-represent (executable) scripts inside of Sling. This interface is
-implemented in the <em>scripting/core</em> bundle in the <em>DefaultSlingScript</em>
-class which also implements the <em>javax.servlet.Servlet</em>.</p>
-<p>To further simplify the access to scripts from the Resource tree, the
-<em>scripting/core</em> bundle registers an <em>AdapterFactory</em> to adapt
-Resources to Scripts and Servlets (the <em>SlingScriptAdapterFactory</em>). In
-fact the adapter factory returns instances of the <em>DefaultSlingScript</em>
-class for both Scripts and Servlets.</p>
-<p>From the perspective of the Servlet resolver, scripts and servlets are
-handled exactly the same. In fact, internally, Sling only handles with
-Servlets, whereas scripts are packed inside a Servlet wrapping and
-representing the script.</p>
-<p><a name="Servlets-"></a></p>
+<p>The Sling API defines a <code>SlingScript</code> interface which is used to represent (executable) scripts inside of Sling. This interface is implemented in the <code>scripting/core</code> bundle in the <code>DefaultSlingScript</code> class which also implements the <code>javax.servlet.Servlet</code>.</p>
+<p>To further simplify the access to scripts from the Resource tree, the <code>scripting/core</code> bundle registers an <code>AdapterFactory</code> to adapt Resources to Scripts and Servlets (the <code>SlingScriptAdapterFactory</code>). In fact the adapter factory returns instances of the <code>DefaultSlingScript</code> class for both Scripts and Servlets.</p>
+<p>From the perspective of the Servlet resolver, scripts and servlets are handled exactly the same. In fact, internally, Sling only handles with Servlets, whereas scripts are packed inside a Servlet wrapping and representing the script.</p>
<h2></h2>
-<p><a name="Servlets-DefaultServlet(s)"></a></p>
<h2 id="default-servlets">Default Servlet(s)</h2>
-<p>As explained in the Resolution Process section above, a default Servlet is
-selected if no servlet (or script) for the current resource type can be
-found. To make the provisioning of a default Servlet as versatile as
-provisioning per resource type Servlets (or scripts), the default Servlet
-is selected with just a special resource type <em>sling/servlet/default</em>.</p>
-<p>The actual Servlet or Script called as the default Servlet is resolved
-exactly the same way as for any resource type. That is, also for the
-default Servlet selection, the request selectors and extension or method
-are considered. Also, the Servlet may be a Servlet registered as an OSGi
-service or it may be a Script stored in the repository or provided by any
-bundle.</p>
-<p>Finally, if not even a registered default Servlet may be resolved for the
-request, because none has been registered, the <em>servlets/resolver</em> bundle
-provides a fall back the <em>DefaultServlet</em> with the following
-functionality:</p>
+<p>As explained in the Resolution Process section above, a default Servlet is selected if no servlet (or script) for the current resource type can be found. To make the provisioning of a default Servlet as versatile as provisioning per resource type Servlets (or scripts), the default Servlet is selected with just a special resource type <code>sling/servlet/default</code>.</p>
+<p>The actual Servlet or Script called as the default Servlet is resolved exactly the same way as for any resource type. That is, also for the default Servlet selection, the request selectors and extension or method are considered. Also, the Servlet may be a Servlet registered as an OSGi service or it may be a Script stored in the repository or provided by any bundle.</p>
+<p>Finally, if not even a registered default Servlet may be resolved for the request, because none has been registered, the <code>servlets/resolver</code> bundle provides a fall back the <code>DefaultServlet</code> with the following functionality:</p>
<ul>
-<li>If an <em>NonExistingResource</em> was created for the request the
-<em>DefaultServlet</em> sends a 404 (Not Found)</li>
-<li>Otherwise the <em>DefaultServlet</em> sends a 500 (Internal Server Error),
-because normally at least a <em>NonExistingResource</em> should be created</li>
+<li>If an <code>NonExistingResource</code> was created for the request the <code>DefaultServlet</code> sends a 404 (Not Found)</li>
+<li>Otherwise the <code>DefaultServlet</code> sends a 500 (Internal Server Error), because normally at least a <code>NonExistingResource</code> should be created</li>
</ul>
-<p><a name="Servlets-OptingServletinterface"></a></p>
<h2 id="optingservlet-interface">OptingServlet interface</h2>
-<p>If a registered servlet implements the OptingServlet interface, Sling uses
-that servlet's <em>accepts(SlingHttpServletRequest request)</em> method to
-refine the servlet resolution process.</p>
-<p>In this case, the servlet is only selected for processing the current
-request if its <em>accept</em> method returns true.</p>
-<p><a name="Servlets-ErrorHandlerServlet(s)orScripts"></a></p>
+<p>If a registered servlet implements the OptingServlet interface, Sling uses that servlet's <code>accepts(SlingHttpServletRequest request)</code> method to refine the servlet resolution process.</p>
+<p>In this case, the servlet is only selected for processing the current request if its <code>accept</code> method returns true.</p>
<h2 id="error-handler-servlets-or-scripts">Error Handler Servlet(s) or Scripts</h2>
-<p>Error handling support is now described on the <a href="errorhandling.html">Errorhandling</a>
- page.</p>
+<p>Error handling support is now described on the <a href="/errorhandling.html">Errorhandling</a> page.</p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
- Rev. 1328899 by fmeschbe on Sun, 22 Apr 2012 16:52:13 +0000
+ Rev. 1341347 by fmeschbe on Tue, 22 May 2012 08:25:18 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project
Modified: websites/staging/sling/trunk/content/sitemap.html
==============================================================================
--- websites/staging/sling/trunk/content/sitemap.html (original)
+++ websites/staging/sling/trunk/content/sitemap.html Tue May 22 08:25:32 2012
@@ -83,7 +83,7 @@
</div>
<h1>Sitemap</h1>
<ul>
-<li><a href="/46-line-blog.html">46 Line Blog</a></li>
+<li><a href="/accessing-filesystem-resources-extensions-fsresource.html">Accessing Filesystem Resources (extensions.fsresource)</a></li>
<li><a href="/adapters.html">Adapters</a></li>
<li><a href="/apache-sling-commons-thread-pool.html">Apache Sling Commons Thread Pool</a></li>
<li><a href="/apache-sling-community-roles-and-processes.html">Apache Sling Community Roles and Processes</a></li>
@@ -91,15 +91,17 @@
<li><a href="/apache-sling.html">Apache Sling</a></li>
<li><a href="/architecture.html">Architecture</a></li>
<li><a href="/assembly.html">Assembly</a></li>
-<li><a href="/authentication---actors.html">Authentication - Actors</a></li>
-<li><a href="/authentication---authenticationhandler.html">Authentication - AuthenticationHandler</a></li>
-<li><a href="/authentication---framework.html">Authentication - Framework</a></li>
-<li><a href="/authentication---tasks.html">Authentication - Tasks</a></li>
+<li><a href="/authentication-actors.html">Authentication - Actors</a></li>
+<li><a href="/authentication-authenticationhandler.html">Authentication - AuthenticationHandler</a></li>
+<li><a href="/authentication-framework.html">Authentication - Framework</a></li>
+<li><a href="/authentication-tasks.html">Authentication - Tasks</a></li>
<li><a href="/authentication.html">Authentication</a></li>
+<li><a href="/bundle-resources-extensions-bundleresource.html">Bundle Resources (extensions.bundleresource)</a></li>
<li><a href="/bundles.html">Bundles</a></li>
<li><a href="/client-request-logging.html">Client Request Logging</a></li>
<li><a href="/commons-html-utilities.html">Commons HTML Utilities</a></li>
<li><a href="/configuration.html">Configuration</a></li>
+<li><a href="/content-loading-jcr-contentloader.html">Content Loading (jcr.contentloader)</a></li>
<li><a href="/contributing.html">Contributing</a></li>
<li><a href="/css">css</a><ul>
<li><a href="/css/site.css">site.css</a></li>
@@ -119,30 +121,32 @@
<li><a href="/filters.html">Filters</a></li>
<li><a href="/form-based-authenticationhandler.html">Form Based AuthenticationHandler</a></li>
<li><a href="/getting-and-building-sling.html">Getting and Building Sling</a></li>
-<li><a href="/getting-resources-and-properties-in-sling.html">Getting Resources and Properties in Sling</a></li>
<li><a href="/getting-started.html">Getting Started</a></li>
<li><a href="/groovy-support.html">Groovy Support</a></li>
<li><a href="/guides.html">Guides</a></li>
-<li><a href="/how-to-manage-events-in-sling.html">How to Manage Events in Sling</a></li>
-<li><a href="/installing-and-upgrading-bundles.html">Installing and Upgrading Bundles</a></li>
+<li><a href="/internationalization-support-i18n.html">Internationalization Support (i18n)</a></li>
<li><a href="/issue-tracker.html">Issue Tracker</a></li>
-<li><a href="/jackrabbit-persistence.html">Jackrabbit Persistence</a></li>
<li><a href="/jcr-installer-provider.html">JCR Installer Provider</a></li>
<li><a href="/jspc.html">JspC</a></li>
<li><a href="/launch-sling.html">Launch Sling</a></li>
<li><a href="/links.html">Links</a></li>
<li><a href="/logging.html">Logging</a></li>
+<li><a href="/managing-permissions-jackrabbit-accessmanager.html">Managing permissions (jackrabbit.accessmanager)</a></li>
+<li><a href="/managing-users-and-groups-jackrabbit-usermanager.html">Managing users and groups (jackrabbit.usermanager)</a></li>
+<li><a href="/manipulating-content-the-slingpostservlet-servlets-post.html">Manipulating Content - The SlingPostServlet (servlets.post)</a></li>
<li><a href="/mappings-for-resource-resolution.html">Mappings for Resource Resolution</a></li>
<li><a href="/maven-archetypes.html">Maven Archetypes</a></li>
<li><a href="/maven-launchpad-plugin.html">Maven Launchpad Plugin</a></li>
<li><a href="/maventipsandtricks.html">MavenTipsAndTricks</a></li>
<li><a href="/media.html">Media</a></li>
+<li><a href="/mime-type-support-commons-mime.html">MIME Type Support (commons.mime)</a></li>
<li><a href="/monitoring-requests.html">Monitoring Requests</a></li>
<li><a href="/navigation.html">Navigation</a></li>
<li><a href="/news.html">News</a></li>
<li><a href="/old-stuff.html">Old Stuff</a></li>
<li><a href="/openid-authenticationhandler.html">OpenID AuthenticationHandler</a></li>
<li><a href="/osgi-installer.html">OSGi Installer</a></li>
+<li><a href="/output-rewriting-pipelines-org-apache-sling-rewriter.html">Output Rewriting Pipelines (org.apache.sling.rewriter)</a></li>
<li><a href="/plugins.html">Plugins</a></li>
<li><a href="/project-information.html">Project Information</a></li>
<li><a href="/project-license.html">Project License</a></li>
@@ -153,12 +157,15 @@
<li><a href="/request-parameters.html">Request Parameters</a></li>
<li><a href="/request-processing.html">Request Processing</a></li>
<li><a href="/resources.html">Resources</a></li>
+<li><a href="/run-modes-org-apache-sling-runmode.html">Run Modes (org.apache.sling.runmode)</a></li>
+<li><a href="/scheduler-service-commons-scheduler.html">Scheduler Service (commons scheduler)</a></li>
<li><a href="/scriptengineintegration.html">ScriptEngineIntegration</a></li>
<li><a href="/security.html">Security</a></li>
<li><a href="/servlet-resolution.html">Servlet Resolution</a></li>
<li><a href="/servlets.html">Servlets</a></li>
<li><a href="/sitemap.html">Sitemap</a></li>
<li><a href="/sling-api.html">Sling API</a></li>
+<li><a href="/sling-settings-org-apache-sling-settings.html">Sling Settings (org.apache.sling.settings)</a></li>
<li><a href="/sling-testing-tools.html">Sling Testing Tools</a></li>
<li><a href="/sling.html">Sling</a></li>
<li><a href="/the-sling-engine.html">The Sling Engine</a><ul>
@@ -166,6 +173,15 @@
</ul>
</li>
<li><a href="/the-sling-launchpad.html">The Sling Launchpad</a></li>
+<li><a href="/tutorials-how-tos.html">Tutorials & How-Tos</a><ul>
+<li><a href="/tutorials-how-tos/46-line-blog.html">46 Line Blog</a></li>
+<li><a href="/tutorials-how-tos/getting-resources-and-properties-in-sling.html">Getting Resources and Properties in Sling</a></li>
+<li><a href="/tutorials-how-tos/how-to-manage-events-in-sling.html">How to Manage Events in Sling</a></li>
+<li><a href="/tutorials-how-tos/installing-and-upgrading-bundles.html">Installing and Upgrading Bundles</a></li>
+<li><a href="/tutorials-how-tos/jackrabbit-persistence.html">Jackrabbit Persistence</a></li>
+<li><a href="/tutorials-how-tos/testing-sling-based-applications.html">Testing Sling-based applications</a></li>
+</ul>
+</li>
<li><a href="/url-decomposition.html">URL decomposition</a></li>
<li><a href="/version-policy.html">Version Policy</a></li>
<li><a href="/web-console-extensions.html">Web Console Extensions</a></li>
Modified: websites/staging/sling/trunk/content/sling-api.html
==============================================================================
--- websites/staging/sling/trunk/content/sling-api.html (original)
+++ websites/staging/sling/trunk/content/sling-api.html Tue May 22 08:25:32 2012
@@ -82,465 +82,290 @@
<a href="/">Home</a>
</div>
<h1>Sling API</h1>
- <p><a name="SlingAPI-TheSlingAPI"></a></p>
-<h1 id="the-sling-api">The Sling API</h1>
+ <h1 id="the-sling-api">The Sling API</h1>
<p>{note:title=Work In Progress}
-The contents of this page is being created at the moment. It contains
-incomplete and partially wrong information as the text is adapted from the
-contents of the <a href="component-api.html">Component API</a>
- documentation page.
+The contents of this page is being created at the moment. It contains incomplete and partially wrong information as the text is adapted from the contents of the <a href="">Component API</a> documentation page.
{note}</p>
-<p><a name="SlingAPI-Introduction"></a></p>
<h2 id="introduction">Introduction</h2>
-<p>The <em>Sling API</em> defines a presentation framework to build Web Applications.
-As such the Sling API builds upon the Servlet API but extends the latter
-with new functionality:</p>
+<p>The <em>Sling API</em> defines a presentation framework to build Web Applications. As such the Sling API builds upon the Servlet API but extends the latter with new functionality:</p>
<ul>
-<li>A web page may be built from many different pieces. This aggregation of
-different pieces is comparable to the functionality provided by the Portlet
-API. In contrast to the latter, though, the pieces may themselves be
-aggregates of yet more pieces. So a single web page response may consist of
-a tree of pieces.</li>
-<li>Just like the Servlet API and the Portlet API the Sling API mainly
-defines a Java based framework. Yet the Sling API comes with the intention
-of supporting scripting built.</li>
-<li>In contrast to the Servlet API and the Portlet API, the Sling API is
-resource centric. That is, the request URL does not address a servlet or a
-portlet but a resource represented by an instance of the
-<em>org.apache.sling.api.resource.Resource</em> interface. From this resource
-the implementation of the Sling API will derive a <em>javax.servlet.Servlet</em>
-or <em>org.apache.sling.api.scripting.SlingScript</em> instance, which is used
-to handle the request.</li>
+<li>A web page may be built from many different pieces. This aggregation of different pieces is comparable to the functionality provided by the Portlet API. In contrast to the latter, though, the pieces may themselves be aggregates of yet more pieces. So a single web page response may consist of a tree of pieces.</li>
+<li>Just like the Servlet API and the Portlet API the Sling API mainly defines a Java based framework. Yet the Sling API comes with the intention of supporting scripting built.</li>
+<li>In contrast to the Servlet API and the Portlet API, the Sling API is resource centric. That is, the request URL does not address a servlet or a portlet but a resource represented by an instance of the <code>org.apache.sling.api.resource.Resource</code> interface. From this resource the implementation of the Sling API will derive a <code>javax.servlet.Servlet</code> or <code>org.apache.sling.api.scripting.SlingScript</code> instance, which is used to handle the request.</li>
</ul>
-<p>An implementation of the presentation framework defined by the Sling API is
-called a <em>Sling Framework</em>. The Apache Sling project actually contains two
-implementations of this API: <em>microsling</em> and <em>Sling</em>. microsling (note the
-lowercase <em>m</em>) implements the same request processing mechanisms as <em>Sling</em>
-but is very hardcoded. It serves well as a rapid development environment as
-it is quickly set up, easy to handle and shows results very easily. Sling
-on the other hand is based on an OSGi framework and very flexible, allowing
-the extension of the system in various ways.</p>
-<p><a name="SlingAPI-GoingResourceCentric"></a></p>
+<p>An implementation of the presentation framework defined by the Sling API is called a <em>Sling Framework</em>. The Apache Sling project actually contains two implementations of this API: <em>microsling</em> and <em>Sling</em>. microsling (note the lowercase <em>m</em>) implements the same request processing mechanisms as <em>Sling</em> but is very hardcoded. It serves well as a rapid development environment as it is quickly set up, easy to handle and shows results very easily. Sling on the other hand is based on an OSGi framework and very flexible, allowing the extension of the system in various ways.</p>
<h2 id="going-resource-centric">Going Resource Centric</h2>
-<p>Traditional web applications are built around the notion of a traditional
-application which is converted into an application which may be used using
-a Web Browser. Web applications consist of a series of servlets and JSP
-scripts, which are called based on configuration in the web application
-deployment descriptor. Such applications are generally based on some
-internal database or some static filesystem content.</p>
-<p>The Sling API on the other hand looks more like a traditional web server
-from the outside, which delivers more or less static content. Thus, while
-the traditional web application uses the request URL to select a piece of
-code to execute, the Sling API uses the URL to select a resource to be
-delivered.</p>
-<p><a name="SlingAPI-ComparsiontotheServletAPI"></a></p>
+<p>Traditional web applications are built around the notion of a traditional application which is converted into an application which may be used using a Web Browser. Web applications consist of a series of servlets and JSP scripts, which are called based on configuration in the web application deployment descriptor. Such applications are generally based on some internal database or some static filesystem content.</p>
+<p>The Sling API on the other hand looks more like a traditional web server from the outside, which delivers more or less static content. Thus, while the traditional web application uses the request URL to select a piece of code to execute, the Sling API uses the URL to select a resource to be delivered.</p>
<h3 id="comparsion-to-the-servlet-api">Comparsion to the Servlet API</h3>
-<p>The Sling API builds upon the Servlet API. Generally a Sling Framework will
-run inside a Servlet Container and be manifested towards the Servlet
-Container as a single Servlet, which dispatches requests to the Servlets
-and Scripts depending on the request URLs.</p>
-<p>Response rendering may itself be a multi-step operation. Depending on the
-Servlets and Scripts, the rendering may include dispatching for child (or
-even foreign) Resources.</p>
-<p><a name="SlingAPI-ComparisiontothePortletAPI"></a></p>
+<p>The Sling API builds upon the Servlet API. Generally a Sling Framework will run inside a Servlet Container and be manifested towards the Servlet Container as a single Servlet, which dispatches requests to the Servlets and Scripts depending on the request URLs.</p>
+<p>Response rendering may itself be a multi-step operation. Depending on the Servlets and Scripts, the rendering may include dispatching for child (or even foreign) Resources.</p>
<h3 id="comparision-to-the-portlet-api">Comparision to the Portlet API</h3>
-<p>Unlike the Portlet API, which defines one single level of portlet hierarchy
-- portlets are just pieces residing besides each other - the Sling API
-allows for hierarchic structuring of Resources and hence Servlet and Script
-renderings. To support this structuring, the Sling Framework does not
-control the rendering process of all elements on the page like the Portlet
-Container does for the portlets. Instead only the Resource addressed by the
-request URL is processed and it is left to the Servlet or Script rendering
-that Resource to dispatch other Resource/Servlet/Script tupels to add more
-data to the response.</p>
-<p><a name="SlingAPI-ToIteratororToEnumeration"></a></p>
+<p>Unlike the Portlet API, which defines one single level of portlet hierarchy - portlets are just pieces residing besides each other - the Sling API allows for hierarchic structuring of Resources and hence Servlet and Script renderings. To support this structuring, the Sling Framework does not control the rendering process of all elements on the page like the Portlet Container does for the portlets. Instead only the Resource addressed by the request URL is processed and it is left to the Servlet or Script rendering that Resource to dispatch other Resource/Servlet/Script tupels to add more data to the response.</p>
<h3 id="to-iterator-or-to-enumeration">To Iterator or To Enumeration</h3>
-<p>With the advent of the Java Collection framework in Java 2, the
-<em>Enumeration</em> has been superceded by the <em>Iterator</em>. So the natural
-choice for the Sling API for methods to return enumeratable collection of
-objects would have be to declare the use of <em>Iterator</em> instances. But
-because the Servlet API defines to use <em>Enumeration</em> instances, the Sling
-API will also declare the use of <em>Enumeration</em> instances for consistency
-with the Servlet API extended by the Sling API.</p>
-<p><a name="SlingAPI-RequestProcessing"></a></p>
+<p>With the advent of the Java Collection framework in Java 2, the <code>Enumeration</code> has been superceded by the <code>Iterator</code>. So the natural choice for the Sling API for methods to return enumeratable collection of objects would have be to declare the use of <code>Iterator</code> instances. But because the Servlet API defines to use <code>Enumeration</code> instances, the Sling API will also declare the use of <code>Enumeration</code> instances for consistency with the Servlet API extended by the Sling API.</p>
<h2 id="request-processing">Request Processing</h2>
-<p>Unlike traditional Servlet API request processing, a Sling API request is
-processed by the Sling Framework in three basic steps:</p>
+<p>Unlike traditional Servlet API request processing, a Sling API request is processed by the Sling Framework in three basic steps:</p>
<ol>
-<li><em>Resource Resolution</em> - The Sling Framework derives a Resource instance
-from the client request URL. The details of how to resolve the Resource.
-One possible solution would be to map the request URL to a <a href="http://www.jcp.org/en/jsr/detail?id=170">Java Content Repository</a>
- Node and return a Resource representing that Node.</li>
-<li><em>Servlet and Script Resolution</em> - From the Resource created in the first
-step, the Servlet or Script is resolved based on the type of the Resource.
-The resource type is a simple string, whose semantics is defined by the
-Sling Framework. One possible definition could be for the resource type to
-be the primary node type of the Node underlying the Resource.</li>
-<li><em>Input Processing and Response Generation</em> - After getting the Resource
-and the Servlet or Script, the <em>service()</em> method is called or the script
-is evaluated to process any user supplied input and send the response to
-the client. To structure the rendered response page, this method is
-responsible to include other resources. See <em>Dispatching Requests</em> below
-for details. See <em>Error Handling</em> below for a discussion on how exceptions
-and HTTP stati are handled.</li>
+<li><em>Resource Resolution</em> - The Sling Framework derives a Resource instance from the client request URL. The details of how to resolve the Resource. One possible solution would be to map the request URL to a <a href="">Java Content Repository</a> Node and return a Resource representing that Node.</li>
+<li><em>Servlet and Script Resolution</em> - From the Resource created in the first step, the Servlet or Script is resolved based on the type of the Resource. The resource type is a simple string, whose semantics is defined by the Sling Framework. One possible definition could be for the resource type to be the primary node type of the Node underlying the Resource.</li>
+<li><em>Input Processing and Response Generation</em> - After getting the Resource and the Servlet or Script, the <code>service()</code> method is called or the script is evaluated to process any user supplied input and send the response to the client. To structure the rendered response page, this method is responsible to include other resources. See <em>Dispatching Requests</em> below for details. See <em>Error Handling</em> below for a discussion on how exceptions and HTTP stati are handled.</li>
</ol>
-<p><a name="SlingAPI-URLdecomposition"></a></p>
<h3 id="url-decomposition">URL decomposition</h3>
-<p>During the <em>Resource Resolution</em> step, the client request URL is decomposed
-into the following parts:</p>
+<p>During the <em>Resource Resolution</em> step, the client request URL is decomposed into the following parts:</p>
<ol>
-<li><em>Resource Path</em> - The longest substring of the request URL resolving to
-a Resource such that the resource path is either the complete request URL
-or the next character in the request URL after the resource path is either
-a dot (<em>.</em>) or a slash (<em>/</em>).</li>
-<li><em>Selectors</em> - If the first character in the request URL after the
-resource path is a dot, the string after the dot upto but not including the
-last dot before the next slash character or the end of the request URL. If
-the resource path spans the complete request URL or if a slash follows the
-resource path in the request URL, no seletors exist. If only one dot
-follows the resource path before the end of the request URL or the next
-slash, no selectors exist.</li>
-<li><em>Extension</em> - The string after the last dot after the resource path in
-the request URL but before the end of the request URL or the next slash
-after the resource path in the request URL. If a slash follows the resource
-path in the request URL, the extension is empty.</li>
-<li><em>Suffix Path</em> - If the request URL contains a slash character after the
-resource path and optional selectors and extension, the path starting with
-the slash upto the end of the request URL is the suffix path. Otherwise,
-the suffix path is empty.</li>
+<li><em>Resource Path</em> - The longest substring of the request URL resolving to a Resource such that the resource path is either the complete request URL or the next character in the request URL after the resource path is either a dot (<code>.</code>) or a slash (<code>/</code>).</li>
+<li><em>Selectors</em> - If the first character in the request URL after the resource path is a dot, the string after the dot upto but not including the last dot before the next slash character or the end of the request URL. If the resource path spans the complete request URL or if a slash follows the resource path in the request URL, no seletors exist. If only one dot follows the resource path before the end of the request URL or the next slash, no selectors exist.</li>
+<li><em>Extension</em> - The string after the last dot after the resource path in the request URL but before the end of the request URL or the next slash after the resource path in the request URL. If a slash follows the resource path in the request URL, the extension is empty.</li>
+<li><em>Suffix Path</em> - If the request URL contains a slash character after the resource path and optional selectors and extension, the path starting with the slash upto the end of the request URL is the suffix path. Otherwise, the suffix path is empty.</li>
</ol>
-<p><em>Examples</em>: Assume there is a Resource at <em>/a/b</em>, which has no children.</p>
+<p><em>Examples</em>: Assume there is a Resource at <code>/a/b</code>, which has no children.</p>
<table>
-<tr><th> URI </th><th> Resource Path </th><th> Selectors </th><th> Extension </th><th> Suffix </th></tr>
-<tr><td> /a/b </td><td> /a/b </td><td> null </td><td> null </td><td> null </td></tr>
-<tr><td> /a/b.html </td><td> /a/b </td><td> null </td><td> html </td><td> null </td></tr>
-<tr><td> /a/b.s1.html </td><td> /a/b </td><td> s1 </td><td> html </td><td> null </td></tr>
-<tr><td> /a/b.s1.s2.html </td><td> /a/b </td><td> s1.s2 </td><td> html </td><td> null </td></tr>
-<tr><td> /a/b/c/d </td><td> /a/b </td><td> null </td><td> null </td><td> /c/d </td></tr>
-<tr><td> /a/b.html/c/d </td><td> /a/b </td><td> null </td><td> html </td><td> /c/d </td></tr>
-<tr><td> /a/b.s1.html/c/d </td><td> /a/b </td><td> s1 </td><td> html </td><td> /c/d </td></tr>
-<tr><td> /a/b.s1.s2.html/c/d </td><td> /a/b </td><td> s1.s2 </td><td> html </td><td> /c/d </td></tr>
-<tr><td> /a/b/c/d.s.txt </td><td> /a/b </td><td> null </td><td> null </td><td> /c/d.s.txt </td></tr>
-<tr><td> /a/b.html/c/d.s.txt </td><td> /a/b </td><td> null </td><td> html </td><td> /c/d.s.txt </td></tr>
-<tr><td> /a/b.s1.html/c/d.s.txt </td><td> /a/b </td><td> s1 </td><td> html </td><td> /c/d.s.txt </td></tr>
-<tr><td> /a/b.s1.s2.html/c/d.s.txt </td><td> /a/b </td><td> s1.s2 </td><td> html </td><td> /c/d.s.txt </td></tr>
+<thead>
+<tr>
+<th>URI</th>
+<th>Resource Path</th>
+<th>Selectors</th>
+<th>Extension</th>
+<th>Suffix</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>/a/b</td>
+<td>/a/b</td>
+<td>null</td>
+<td>null</td>
+<td>null</td>
+</tr>
+<tr>
+<td>/a/b.html</td>
+<td>/a/b</td>
+<td>null</td>
+<td>html</td>
+<td>null</td>
+</tr>
+<tr>
+<td>/a/b.s1.html</td>
+<td>/a/b</td>
+<td>s1</td>
+<td>html</td>
+<td>null</td>
+</tr>
+<tr>
+<td>/a/b.s1.s2.html</td>
+<td>/a/b</td>
+<td>s1.s2</td>
+<td>html</td>
+<td>null</td>
+</tr>
+<tr>
+<td>/a/b/c/d</td>
+<td>/a/b</td>
+<td>null</td>
+<td>null</td>
+<td>/c/d</td>
+</tr>
+<tr>
+<td>/a/b.html/c/d</td>
+<td>/a/b</td>
+<td>null</td>
+<td>html</td>
+<td>/c/d</td>
+</tr>
+<tr>
+<td>/a/b.s1.html/c/d</td>
+<td>/a/b</td>
+<td>s1</td>
+<td>html</td>
+<td>/c/d</td>
+</tr>
+<tr>
+<td>/a/b.s1.s2.html/c/d</td>
+<td>/a/b</td>
+<td>s1.s2</td>
+<td>html</td>
+<td>/c/d</td>
+</tr>
+<tr>
+<td>/a/b/c/d.s.txt</td>
+<td>/a/b</td>
+<td>null</td>
+<td>null</td>
+<td>/c/d.s.txt</td>
+</tr>
+<tr>
+<td>/a/b.html/c/d.s.txt</td>
+<td>/a/b</td>
+<td>null</td>
+<td>html</td>
+<td>/c/d.s.txt</td>
+</tr>
+<tr>
+<td>/a/b.s1.html/c/d.s.txt</td>
+<td>/a/b</td>
+<td>s1</td>
+<td>html</td>
+<td>/c/d.s.txt</td>
+</tr>
+<tr>
+<td>/a/b.s1.s2.html/c/d.s.txt</td>
+<td>/a/b</td>
+<td>s1.s2</td>
+<td>html</td>
+<td>/c/d.s.txt</td>
+</tr>
+</tbody>
</table>
-
<p>{info:title=Automated tests and examples}
-The <a href="http://svn.apache.org/repos/asf/sling/trunk/bundles/engine/src/test/java/org/apache/sling/engine/impl/request/SlingRequestPathInfoTest.java">SlingRequestPathInfoTest</a>
- demonstrates and tests this decomposition. Feel free to suggest additional
-tests that help clarify how this works!
+The <a href="">SlingRequestPathInfoTest</a> demonstrates and tests this decomposition. Feel free to suggest additional tests that help clarify how this works!
{info}</p>
-<p><a name="SlingAPI-TheSlingHttpServletRequest"></a></p>
<h2 id="the-slinghttpservletrequest">The SlingHttpServletRequest</h2>
-<p>The <em>org.apache.sling.api.SlingHttpServletRequest</em> interface defines the
-basic data available from the client request to both action processing and
-response rendering. The <em>SlingHttpServletRequest</em> extends the
-<em>javax.servlet.http.HTTPServletRequest</em>.</p>
-<p>This section describes the data available from the
-<em>SlingHttpServletRequest</em>. For a complete and normative description of
-the methods, refer to the Sling API JavaDoc. The following information is
-represented for reference. In the case of differences between the following
-descriptions and the Sling API JavaDoc, the latter takes precedence.</p>
+<p>The <code>org.apache.sling.api.SlingHttpServletRequest</code> interface defines the basic data available from the client request to both action processing and response rendering. The <code>SlingHttpServletRequest</code> extends the <code>javax.servlet.http.HTTPServletRequest</code>.</p>
+<p>This section describes the data available from the <code>SlingHttpServletRequest</code>. For a complete and normative description of the methods, refer to the Sling API JavaDoc. The following information is represented for reference. In the case of differences between the following descriptions and the Sling API JavaDoc, the latter takes precedence.</p>
<ol>
-<li><em>Resource access</em> - Resources may be accessed from the
-<em>SlingHttpServletRequest</em> object through the following methods:
-<em>getResource()</em>, <em>getResourceResolver()</em>.</li>
-<li><em>Request URL information</em> - In addition to the standard
-<em>HttpServletRequest</em> information the <em>SlingHttpServletRequest</em> provides
-access to the selectors, extension and suffix through the
-<em>getRequestPathInfo()</em> method. Note that the Resource path is not
-directly available form the <em>SlingHttpServletRequest</em> object. Instead it
-is available through the <em>Resource.getPath()</em> method of the Resource
-object retrieved through <em>SlingHttpServletRequest.getResource()</em>.</li>
-<li><em>Request Parameters</em> - To support user input submitted as
-<em>multipart/form-data</em> encoded POST parameters, the Sling API intrduces
-the <em>RequestParameter</em> interface allowing file uploads. Request
-parameters represented as <em>RequestParameter</em> objects are returned by the
-following methods: <em>getRequestParameter(String name)</em>,
-<em>getRequestParameterMap()</em>, <em>getRequestParameters(String name)</em>.</li>
-<li><em>Request Dispatching</em> - In addition to standard Serlvet API request
-dispatching, the Sling API supports dispatching requests to render
-different Resources using <em>RequestDispatcher</em> objects returned by the
-methods: <em>getRequestDispatcher(Resource resource)</em> and
-.</li>
-<li><em>Miscellaneous</em> - Finally the ComponentRequest interface provides the
-following methods: <em>getCookie(String name)</em>,
-<em>getRequestProgressTracker()</em>, <em>getResponseContentType()</em>,
-<em>getResponseContentTypes()</em>, <em>getResourceBundle(Locale locale)</em>,
-<em>getServiceLocator()</em>.</li>
+<li><em>Resource access</em> - Resources may be accessed from the <code>SlingHttpServletRequest</code> object through the following methods: <code>getResource()</code>, <code>getResourceResolver()</code>.</li>
+<li><em>Request URL information</em> - In addition to the standard <code>HttpServletRequest</code> information the <code>SlingHttpServletRequest</code> provides access to the selectors, extension and suffix through the <code>getRequestPathInfo()</code> method. Note that the Resource path is not directly available form the <code>SlingHttpServletRequest</code> object. Instead it is available through the <code>Resource.getPath()</code> method of the Resource object retrieved through <code>SlingHttpServletRequest.getResource()</code>.</li>
+<li><em>Request Parameters</em> - To support user input submitted as <code>multipart/form-data</code> encoded POST parameters, the Sling API intrduces the <code>RequestParameter</code> interface allowing file uploads. Request parameters represented as <code>RequestParameter</code> objects are returned by the following methods: <code>getRequestParameter(String name)</code>, <code>getRequestParameterMap()</code>, <code>getRequestParameters(String name)</code>.</li>
+<li><em>Request Dispatching</em> - In addition to standard Serlvet API request dispatching, the Sling API supports dispatching requests to render different Resources using <code>RequestDispatcher</code> objects returned by the methods: <code>getRequestDispatcher(Resource resource)</code> and <code>getRequestDispatcher(Resource resource, RequestDispatcherOptions options)</code>.</li>
+<li><em>Miscellaneous</em> - Finally the ComponentRequest interface provides the following methods: <code>getCookie(String name)</code>, <code>getRequestProgressTracker()</code>, <code>getResponseContentType()</code>, <code>getResponseContentTypes()</code>, <code>getResourceBundle(Locale locale)</code>, <code>getServiceLocator()</code>.</li>
</ol>
-<p>The <em>SlingHttpServletRequest</em> objects are only valid during the time of
-request processing. Servlets and Scripts must not keep references for later
-use. As such, the <em>SlingHttpServletRequest</em> interface and its extensions
-are defined to not be thread safe.</p>
-<p><em>A note on HTTP Sessions</em>: The <em>SlingHttpServletRequest</em> extends the
-<em>HttpSerlvetRequest</em> and thus supports standard HTTP sessions. Be aware,
-though that Sessions are server side sessions and hence violate the
-sessionless principle of REST and therefore should be used with care. It is
-almost always possible to not use sessions.</p>
-<p><a name="SlingAPI-TheSlingHttpServletResponse"></a></p>
+<p>The <code>SlingHttpServletRequest</code> objects are only valid during the time of request processing. Servlets and Scripts must not keep references for later use. As such, the <code>SlingHttpServletRequest</code> interface and its extensions are defined to not be thread safe.</p>
+<p><em>A note on HTTP Sessions</em>: The <code>SlingHttpServletRequest</code> extends the <code>HttpSerlvetRequest</code> and thus supports standard HTTP sessions. Be aware, though that Sessions are server side sessions and hence violate the sessionless principle of REST and therefore should be used with care. It is almost always possible to not use sessions.</p>
<h2 id="the-slinghttpservletresponse">The SlingHttpServletResponse</h2>
-<p>The <em>org.apache.sling.api.SlingHttpServletResponse</em> interface extends the
-<em>javax.servet.http.HttpServletResponse</em> interface and is currently empty.
-It merely exists for symmetry with the <em>SlingHttpServletRequest</em>.</p>
-<p><a name="SlingAPI-TheResource"></a></p>
+<p>The <code>org.apache.sling.api.SlingHttpServletResponse</code> interface extends the <code>javax.servet.http.HttpServletResponse</code> interface and is currently empty. It merely exists for symmetry with the <code>SlingHttpServletRequest</code>.</p>
<h2 id="the-resource">The Resource</h2>
-<p>The <em>org.apache.sling.resource.Resource</em> represents the data addressed by
-the request URL. Resources may also be retrieved through the
-<em>org.apache.sling.api.resource.ResourceResolver</em>. Usually this interface
-is not implemented by clients. In certain use cases we call <em>synthetic
-Resource</em> if may be usefull to define a simple object implementing the
-<em>Resource</em> interface. The Sling Framework does not care about the
-concrete implementation of the <em>Resource</em> interface and rather uses the
-defined methods to access required information. The interface defines the
-following methods:</p>
+<p>The <code>org.apache.sling.resource.Resource</code> represents the data addressed by the request URL. Resources may also be retrieved through the <code>org.apache.sling.api.resource.ResourceResolver</code>. Usually this interface is not implemented by clients. In certain use cases we call <em>synthetic Resource</em> if may be usefull to define a simple object implementing the <code>Resource</code> interface. The Sling Framework does not care about the concrete implementation of the <code>Resource</code> interface and rather uses the defined methods to access required information. The interface defines the following methods:</p>
<ol>
-<li><em>getResourceType()</em> - Returns the type of the resource. This resource
-type is used to resolve the Servlet or Script used to handle the request
-for the resource.</li>
-<li><em>getPath()</em> - Returns the path derived from the client request URL which
-led to the creation of the Resource instance. See the <a href="#url_decomposition-url-decomposition.html">#URL_decomposition URL decomposition</a>
- section above for more information. It is not required, that the Resource
-path be a part of the original client request URL. The request URL may also
-have been mapped to some internal path.</li>
-<li><em>getResourceMetadata()</em> - Returns meta data information about the
-resource in a <em>ResourceMetadata</em> object.</li>
-<li><em>adaptTo(Class<AdapterType> type)</em> - Returns alternative representations
-of the Resource. The concrete supported classes to which the Resource may
-be adapted depends on the implementation. For example a Resource based on a
-JCR Node may support being adapted to the underlying Node, an
-<em>InputStream</em>, an <em>URL</em> or even to a mapped object through JCR Object
-Content Mapping.</li>
+<li><em>getResourceType()</em> - Returns the type of the resource. This resource type is used to resolve the Servlet or Script used to handle the request for the resource.</li>
+<li><em>getPath()</em> - Returns the path derived from the client request URL which led to the creation of the Resource instance. See the <a href="">#URL_decomposition URL decomposition</a> section above for more information. It is not required, that the Resource path be a part of the original client request URL. The request URL may also have been mapped to some internal path.</li>
+<li><em>getResourceMetadata()</em> - Returns meta data information about the resource in a <code>ResourceMetadata</code> object.</li>
+<li><em>adaptTo(Class<AdapterType> type)</em> - Returns alternative representations of the Resource. The concrete supported classes to which the Resource may be adapted depends on the implementation. For example a Resource based on a JCR Node may support being adapted to the underlying Node, an <code>InputStream</code>, an <code>URL</code> or even to a mapped object through JCR Object Content Mapping.</li>
</ol>
<hr />
-<p><a name="SlingAPI-TheComponent"></a></p>
<h2 id="the-component">The Component</h2>
-<p>The <em>org.apache.sling.component.Component</em> interface defines the API
-implemented to actually handle requests. As such the Component interface is
-comparable to the =javax.servlet.Servlet= interface. Like those other
-interfaces, the Component interface provides methods for life cycle
-management: <em>init(ComponentContext context)</em>, <em>destroy()</em>.</p>
-<p><a name="SlingAPI-ProcessingtheRequest"></a></p>
+<p>The <code>org.apache.sling.component.Component</code> interface defines the API implemented to actually handle requests. As such the Component interface is comparable to the =javax.servlet.Servlet= interface. Like those other interfaces, the Component interface provides methods for life cycle management: <code>init(ComponentContext context)</code>, <code>destroy()</code>.</p>
<h3 id="processing-the-request">Processing the Request</h3>
-<p>The Component Framework calls the method of the Component to have the component
-process the request optionally processing user input, rendering the
-response and optionally dispatch to other Content/Component tuples to
-provide more response data.</p>
-<p><a name="SlingAPI-ContentanditsComponent"></a></p>
+<p>The Component Framework calls the <code>service(ComponentRequest request, ComponentResponse response)</code> method of the Component to have the component process the request optionally processing user input, rendering the response and optionally dispatch to other Content/Component tuples to provide more response data.</p>
<h3 id="content-and-its-component">Content and its Component</h3>
-<p>The Content object and a Component form a pair, in which the Content object
-takes the passive part of providing data to the Component and the Component
-takes the active part of acting upon the Content object. As a consequence,
-there always exists a link between a given implementation of the Content
-interface and a given implementation of the Component interface.</p>
-<p>This link is manifested by the Component identifier available from the
-Content object through the <em>Content.getComponentId()</em> method on the one
-hand. On the other hand, the link is manifested by the
-<em>getContentClassName()</em> and <em>createContentInstance()</em> methods of the
-Component interface.</p>
-<p><a name="SlingAPI-ComponentLifecylce"></a></p>
+<p>The Content object and a Component form a pair, in which the Content object takes the passive part of providing data to the Component and the Component takes the active part of acting upon the Content object. As a consequence, there always exists a link between a given implementation of the Content interface and a given implementation of the Component interface.</p>
+<p>This link is manifested by the Component identifier available from the Content object through the <code>Content.getComponentId()</code> method on the one hand. On the other hand, the link is manifested by the <code>getContentClassName()</code> and <code>createContentInstance()</code> methods of the Component interface.</p>
<h3 id="component-lifecylce">Component Lifecylce</h3>
-<p>When a Component instance is created and added to the Component framework,
-the <em>init(ComponentContext)</em> method is called to prepare and initialize
-the Component. If this method terminates abnormally by throwing an
-exception, the Component is not used. The Component Framework
-implementation may try at a later time to recreate the Component, intialize
-it and use it. If the Component Framework tries to recreate the Component a
-new instance of the Component must be created to be initialized and used.</p>
-<p>When the Component has successfully been initialized, it may be referred to
-by Content objects. When a client request is to be processed, the Content
-object is resolved and the <em>service</em> method on the Component to which the
-Content object refers is called. The <em>service</em> method may - and generally
-will - be called simultaneously to handle different requests in different
-threads. As such, implementations of these methods must be thread safe.</p>
-<p>When the Component Framework decides to take a Component out of service,
-the <em>destroy()</em> method is called to give the Component a chance to
-cleanup any held resources. The destroy method must only be called by the
-Component Framework when no more request processing is using the Component,
-that is no thread may be in the <em>service</em> method of a Component to be
-destroyed. Irrespective of whether the destroy method terminated normally
-or abnormally, the Component will not be used again.</p>
-<p>The addition and removal of Components is at the discretion of the
-Component Framework. A Component may be loaded at framework start time or
-on demand and my be removed at any time. But only one single Component
-instance with the same Component identifier may be active at the same time
-within a single Component Framework instance.</p>
-<p><a name="SlingAPI-TheComponentExtension"></a></p>
+<p>When a Component instance is created and added to the Component framework, the <code>init(ComponentContext)</code> method is called to prepare and initialize the Component. If this method terminates abnormally by throwing an exception, the Component is not used. The Component Framework implementation may try at a later time to recreate the Component, intialize it and use it. If the Component Framework tries to recreate the Component a new instance of the Component must be created to be initialized and used.</p>
+<p>When the Component has successfully been initialized, it may be referred to by Content objects. When a client request is to be processed, the Content object is resolved and the <code>service</code> method on the Component to which the Content object refers is called. The <code>service</code> method may - and generally will - be called simultaneously to handle different requests in different threads. As such, implementations of these methods must be thread safe.</p>
+<p>When the Component Framework decides to take a Component out of service, the <code>destroy()</code> method is called to give the Component a chance to cleanup any held resources. The destroy method must only be called by the Component Framework when no more request processing is using the Component, that is no thread may be in the <code>service</code> method of a Component to be destroyed. Irrespective of whether the destroy method terminated normally or abnormally, the Component will not be used again.</p>
+<p>The addition and removal of Components is at the discretion of the Component Framework. A Component may be loaded at framework start time or on demand and my be removed at any time. But only one single Component instance with the same Component identifier may be active at the same time within a single Component Framework instance.</p>
<h3 id="the-componentextension">The ComponentExtension</h3>
-<p>To enhance the core functionality of Components, each Component may have
-zero, one ore more Component Extensions attached. A Component Extensions is
-a Java object implementing the
-<em>org.apache.sling.component.ComponentExtension</em> interface. This interface
-just defines a <em>getName()</em> method to identify extensions.</p>
-<p>The concrete implementation as well as instantiation and management of
-Component Extensions is left to the Component Framework implementation with
-one restriction though: The extensions must be available to the Component
-at the time the <em>init(ComponentContext)</em> method is called may only be
-dropped after the <em>destroy()</em> method terminates.</p>
-<p>The Component interface defines two methods to access Extensions: The
-<em>getExtensions()</em> method returns a <em>java.util.Enumeration</em> of all
-ComponentExtension objects attached to the component. If no Component
-Extension are attached to the Component, an empty enumeration is returned.
-The <em>getExtension(String name)</em> returns the named Component Extension
-attached to the Component or <em>null</em> if no such Component Extension is
-attached to the Component.</p>
-<p>Component Frameworks are allowed to share Component Extension instances of
-the same name between different Component instances. Regardless of whether
-Component Extensions are shared or not, they must be thread safe, as any
-Component Extension may be used within the <em>service</em> method, which
-themselves may be called concurrently.</p>
-<p><a name="SlingAPI-RequestProcessingFilters"></a></p>
+<p>To enhance the core functionality of Components, each Component may have zero, one ore more Component Extensions attached. A Component Extensions is a Java object implementing the <code>org.apache.sling.component.ComponentExtension</code> interface. This interface just defines a <code>getName()</code> method to identify extensions.</p>
+<p>The concrete implementation as well as instantiation and management of Component Extensions is left to the Component Framework implementation with one restriction though: The extensions must be available to the Component at the time the <code>init(ComponentContext)</code> method is called may only be dropped after the <code>destroy()</code> method terminates.</p>
+<p>The Component interface defines two methods to access Extensions: The <code>getExtensions()</code> method returns a <code>java.util.Enumeration</code> of all ComponentExtension objects attached to the component. If no Component Extension are attached to the Component, an empty enumeration is returned. The <code>getExtension(String name)</code> returns the named Component Extension attached to the Component or <code>null</code> if no such Component Extension is attached to the Component.</p>
+<p>Component Frameworks are allowed to share Component Extension instances of the same name between different Component instances. Regardless of whether Component Extensions are shared or not, they must be thread safe, as any Component Extension may be used within the <code>service</code> method, which themselves may be called concurrently.</p>
<h2 id="request-processing-filters">Request Processing Filters</h2>
-<p>Similar to the Servlet API providing filters for filtering requests and/or
-responses the Component API provides the
-<em>org.apache.sling.component.ComponentFilter</em> interface. The filters are
-called by a <em>ComponentFilterChain</em> and either handle the request,
-manipulate the request and/or response object and finally forward the
-request and response optionally wrapped to the
-<em>ComponentFilterChain.doFilter(ComponentRequest, ComponentResponse)</em>
-method.</p>
-<p>Like the <em>Component</em>s filters have a defined lifecycle manifested by
-<em>init</em> and <em>destroy</em> methods. When the filter enters the system, the
-Component Framework calls the <em>ComponentFilter.init(ComponentContext)</em>
-method. Only when this method completes successfully will the filter be put
-into action and be used during request processing. When the filter leaves
-the system, the Component Framework removes the filter from being used in
-filter chains and calls the <em>ComponentFilter.destroy()</em> method. This
-method is not expected to throw any exceptions. The filter may be removed
-from the Component Framework at the discretion of the Component Framework
-or because the filter is being unregistered from the Component Framework by
-some means outside this specification.</p>
-<p>This specification does not define how <em>ComponentFilter</em> objects are
-registered with the Component Framework nor is it specified how the order
-in which the filters are called is defined. Likewise it is outside this
-specification how the filter instances registered with the Component
-Framework are configured.</p>
-<p><a name="SlingAPI-Sessions"></a></p>
+<p>Similar to the Servlet API providing filters for filtering requests and/or responses the Component API provides the <code>org.apache.sling.component.ComponentFilter</code> interface. The filters are called by a <code>ComponentFilterChain</code> and either handle the request, manipulate the request and/or response object and finally forward the request and response optionally wrapped to the <code>ComponentFilterChain.doFilter(ComponentRequest, ComponentResponse)</code> method.</p>
+<p>Like the <code>Component</code>s filters have a defined lifecycle manifested by <code>init</code> and <code>destroy</code> methods. When the filter enters the system, the Component Framework calls the <code>ComponentFilter.init(ComponentContext)</code> method. Only when this method completes successfully will the filter be put into action and be used during request processing. When the filter leaves the system, the Component Framework removes the filter from being used in filter chains and calls the <code>ComponentFilter.destroy()</code> method. This method is not expected to throw any exceptions. The filter may be removed from the Component Framework at the discretion of the Component Framework or because the filter is being unregistered from the Component Framework by some means outside this specification.</p>
+<p>This specification does not define how <code>ComponentFilter</code> objects are registered with the Component Framework nor is it specified how the order in which the filters are called is defined. Likewise it is outside this specification how the filter instances registered with the Component Framework are configured.</p>
<h2 id="sessions">Sessions</h2>
-<p>The <em>org.apache.sling.component.ComponentSession</em> interface provides a
-way to identify a user across more than one request and to store transient
-information about that user.</p>
-<p>A component can bind an object attribute into a <em>ComponentSession</em> by
-name. The <em>ComponentSession</em> interface defines two scopes for storing
-objects: <em>APPLICATION_SCOPE</em>, <em>COMPONENT_SCOPE</em>. All objects stored in
-the session using the <em>APPLICATION_SCOPE</em> must be available to all the
-components, servlets and JSPs that belong to the same component application
-and that handle a request identified as being a part of the same session.
-Objects stored in the session using the <em>COMPONENT_SCOPE</em> must be
-available to the component during requests for the same content that the
-objects where stored from. Attributes stored in the <em>COMPONENT_SCOPE</em> are
-not protected from other web components of the component application. They
-are just conveniently namespaced.</p>
-<p>The component session extends the Servlet API <em>HttpSession</em>. Therefore
-all <em>HttpSession</em> listeners do apply to the component session and
-attributes set in the component session are visible in the <em>HttpSession</em>
-and vice versa.</p>
-<p>The attribute accessor methods without the <em>scope</em> parameter always refer
-to <em>COMPONENT_SCOPE</em> attributes. To access <em>APPLICATION_SCOPE</em>
-attributes use the accessors taking an explicit <em>scope</em> parameter.</p>
-<p><em>A final note on Sessions</em>: Sessions are server side sessions and hence
-violate the sessionless principle of REST and therefore should be used with
-care. It is almost always possible to not use sessions.</p>
-<p><a name="SlingAPI-DispatchingRequests"></a></p>
+<p>The <code>org.apache.sling.component.ComponentSession</code> interface provides a way to identify a user across more than one request and to store transient information about that user.</p>
+<p>A component can bind an object attribute into a <code>ComponentSession</code> by name. The <code>ComponentSession</code> interface defines two scopes for storing objects: <code>APPLICATION*SCOPE</code>, <code>COMPONENT*SCOPE</code>. All objects stored in the session using the <code>APPLICATION*SCOPE</code> must be available to all the components, servlets and JSPs that belong to the same component application and that handle a request identified as being a part of the same session. Objects stored in the session using the <code>COMPONENT*SCOPE</code> must be available to the component during requests for the same content that the objects where stored from. Attributes stored in the <code>COMPONENT_SCOPE</code> are not protected from other web components of the component application. They are just conveniently namespaced.</p>
+<p>The component session extends the Servlet API <code>HttpSession</code>. Therefore all <code>HttpSession</code> listeners do apply to the component session and attributes set in the component session are visible in the <code>HttpSession</code> and vice versa.</p>
+<p>The attribute accessor methods without the <em>scope</em> parameter always refer to <code>COMPONENT*SCOPE</code> attributes. To access <code>APPLICATION*SCOPE</code> attributes use the accessors taking an explicit <code>scope</code> parameter.</p>
+<p><em>A final note on Sessions</em>: Sessions are server side sessions and hence violate the sessionless principle of REST and therefore should be used with care. It is almost always possible to not use sessions.</p>
<h2 id="dispatching-requests">Dispatching Requests</h2>
-<p>To include renderings of child Content objects, a
-<em>org.apache.sling.component.ComponentRequestDispatcher</em> object may be
-retrieved from the ComponentContext with which the Component has been
-initialized or from the ComponentRequest provided to the service method.
-Using this dispatcher the reponse of rendering the Content may be included
-by calling the method.</p>
-<p>This method is comparable to the
-<em>RequestDispatcher.include(ServletRequest, ServletResponse</em> method of the
-Servlet API but dispatching by the <em>ComponentRequestDispatcher</em> does not
-go through the servlet container and stays within the Component Framework.</p>
-<p>The <em>service</em> method of included Components are called with an instance
-of the <em>ComponentRequest</em> interface whose <em>getContent()</em> returns the
-Content object for the included Content.</p>
-<p>When a Component is included by another component the following request
-attributes are set:</p>
+<p>To include renderings of child Content objects, a <code>org.apache.sling.component.ComponentRequestDispatcher</code> object may be retrieved from the ComponentContext with which the Component has been initialized or from the ComponentRequest provided to the service method. Using this dispatcher the reponse of rendering the Content may be included by calling the <code>ComponentRequestDispatcher.include(ComponentRequest, ComponentResponse)</code> method.</p>
+<p>This method is comparable to the <code>RequestDispatcher.include(ServletRequest, ServletResponse</code> method of the Servlet API but dispatching by the <code>ComponentRequestDispatcher</code> does not go through the servlet container and stays within the Component Framework.</p>
+<p>The <code>service</code> method of included Components are called with an instance of the <code>ComponentRequest</code> interface whose <code>getContent()</code> returns the Content object for the included Content.</p>
+<p>When a Component is included by another component the following request attributes are set:</p>
<table>
-<tr><th> *Request Attributes* </th><th> *Type* </th><th> *Description* </th></tr>
-<tr><td> *org.apache.sling.component.request.content* </td><td> String </td><td> The *Content*
-instance to which the client URL resolved. This attribute is set when
-included Components are being rendered and it is not set for the Component
-directly addressed by the client request. </td></tr>
-<tr><td> *org.apache.sling.component.request.component* </td><td> String </td><td> The
-*Component* instance for the *Content* object to which the client URL
-resolved. This attribute is set when included Components are being rendered
-and it is not set for the Component directly addressed by the client
-request. </td></tr>
+<thead>
+<tr>
+<th><em>Request Attributes</em></th>
+<th><em>Type</em></th>
+<th><em>Description</em></th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td><code>org.apache.sling.component.request.content</code></td>
+<td>String</td>
+<td>The <code>Content</code> instance to which the client URL resolved. This attribute is set when included Components are being rendered and it is not set for the Component directly addressed by the client request.</td>
+</tr>
+<tr>
+<td><code>org.apache.sling.component.request.component</code></td>
+<td>String</td>
+<td>The <code>Component</code> instance for the <code>Content</code> object to which the client URL resolved. This attribute is set when included Components are being rendered and it is not set for the Component directly addressed by the client request.</td>
+</tr>
+</tbody>
</table>
-
-<p><a name="SlingAPI-ErrorHandling"></a></p>
<h3 id="error-handling">Error Handling</h3>
-<p>While processing requests, the <em>service</em> methods called may have
-problems. Components have multiple options of reporting issues during
-processing to the client:</p>
+<p>While processing requests, the <code>service</code> methods called may have problems. Components have multiple options of reporting issues during processing to the client:</p>
<ul>
-<li>Set the status of the HTTP response calling the
-<em>ComponentResponse.setStatus</em> method</li>
-<li>Send an error page calling the <em>ComponentResponse.sendError</em> method</li>
+<li>Set the status of the HTTP response calling the <code>ComponentResponse.setStatus</code> method</li>
+<li>Send an error page calling the <code>ComponentResponse.sendError</code> method</li>
<li>Throw an exception</li>
</ul>
-<p>If such an exception is thrown, the Component Framework must act upon the
-exception in one of the following ways:</p>
+<p>If such an exception is thrown, the Component Framework must act upon the exception in one of the following ways:</p>
<ul>
-<li>If the request is processed through Servlet API request inclusion, the
-exception must be given back to the servlet container. A
-<em>ComponentException</em> is just forwarded as a <em>ServletException</em>. This is
-a requirement of the Servlet API specification which states for included
-requests:</li>
+<li>If the request is processed through Servlet API request inclusion, the exception must be given back to the servlet container. A <code>ComponentException</code> is just forwarded as a <code>ServletException</code>. This is a requirement of the Servlet API specification which states for included requests:</li>
</ul>
<p>{quote}</p>
<p>{quote}</p>
<ul>
-<li>Otherwise, the Component Framework may handle the error itself in a
-manner similar to the error handling approach defined the Servlet API
-specification (Section SRV 9.9 Error Handling of the Java Servlet
-Specification 2.4). Specifically the request attributes defined by the
-Servlet API specification must be set for the error handler:</li>
+<li>Otherwise, the Component Framework may handle the error itself in a manner similar to the error handling approach defined the Servlet API specification (Section SRV 9.9 Error Handling of the Java Servlet Specification 2.4). Specifically the request attributes defined by the Servlet API specification must be set for the error handler:</li>
</ul>
<table>
-<tr><th> *Request Attributes* </th><th> *Type* </th><th> *Description* </th></tr>
-<tr><td> *javax.servlet.error.status_code* </td><td> *java.lang.Integer* </td><td> The status
-code of the response. In the case of an exception thrown from the
-*service*, the code is defined by the Component Framework. </td></tr>
-<tr><td> *javax.servlet.error.exception_type* </td><td> *java.lang.Class* </td><td> The fully
-qualified name of the exception class thrown. This attribute does not
-exist, if error handling does not result from an exception. This attribute
-is maintained for backwards compatibility according to the Servlet API
-Specification. </td></tr>
-<tr><td> *javax.servlet.error.message* </td><td> *java.lang.String* </td><td> The message of
-the exception thrown. This attribute does not exist, if error handling does
-not result from an exception. This attribute is maintained for backwards
-compatibility according to the Servlet API Specification. </td></tr>
-<tr><td> *javax.servlet.error.exception* </td><td> *java.lang.Throwable* </td><td> The
-exception thrown. This attribute does not exist, if error handling does not
-result from an exception. </td></tr>
-<tr><td> *javax.servlet.error.request_uri* </td><td> *java.lang.String* </td><td> The request
-URL whose processing resulted in the error. </td></tr>
-<tr><td> *javax.servlet.error.servlet_name* </td><td> *java.lang.String* </td><td> The name of
-the servlet which yielded the error. The servlet name will generally not
-have any significance inside the Component Framework. </td></tr>
-<tr><td> *org.apache.sling.component.error.componentId* </td><td> *java.lang.String* </td><td>
-The identifier of the Component whose *service* method has caused the
-error. This attribute does not exist, if the Component Framework itself
-caused the error processing. </td></tr>
-* If the Component Framework decides to not handle the error itself, the
-exception must be forwarded to the servlet container as a
-*ComponentException* wrapping the original exception as its root cause.
+<thead>
+<tr>
+<th><em>Request Attributes</em></th>
+<th><em>Type</em></th>
+<th><em>Description</em></th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td><code>javax.servlet.error.status_code</code></td>
+<td><code>java.lang.Integer</code></td>
+<td>The status code of the response. In the case of an exception thrown from the <code>service</code>, the code is defined by the Component Framework.</td>
+</tr>
+<tr>
+<td><code>javax.servlet.error.exception_type</code></td>
+<td><code>java.lang.Class</code></td>
+<td>The fully qualified name of the exception class thrown. This attribute does not exist, if error handling does not result from an exception. This attribute is maintained for backwards compatibility according to the Servlet API Specification.</td>
+</tr>
+<tr>
+<td><code>javax.servlet.error.message</code></td>
+<td><code>java.lang.String</code></td>
+<td>The message of the exception thrown. This attribute does not exist, if error handling does not result from an exception. This attribute is maintained for backwards compatibility according to the Servlet API Specification.</td>
+</tr>
+<tr>
+<td><code>javax.servlet.error.exception</code></td>
+<td><code>java.lang.Throwable</code></td>
+<td>The exception thrown. This attribute does not exist, if error handling does not result from an exception.</td>
+</tr>
+<tr>
+<td><code>javax.servlet.error.request_uri</code></td>
+<td><code>java.lang.String</code></td>
+<td>The request URL whose processing resulted in the error.</td>
+</tr>
+<tr>
+<td><code>javax.servlet.error.servlet_name</code></td>
+<td><code>java.lang.String</code></td>
+<td>The name of the servlet which yielded the error. The servlet name will generally not have any significance inside the Component Framework.</td>
+</tr>
+<tr>
+<td><code>org.apache.sling.component.error.componentId</code></td>
+<td><code>java.lang.String</code></td>
+<td>The identifier of the Component whose <code>service</code> method has caused the error. This attribute does not exist, if the Component Framework itself caused the error processing.</td>
+</tr>
+<tr>
+<td>* If the Component Framework decides to not handle the error itself, the exception must be forwarded to the servlet container as a <code>ComponentException</code> wrapping the original exception as its root cause.</td>
+<td></td>
+<td></td>
+</tr>
+</tbody>
</table>
-
-<p>This specification does not define, how error handlers are configured and
-used if the Component Framework provides error handling support. Likewise
-the Component Framework may or may not implement support to handle calls to
-the <em>ComponentResponse.sendError</em> method. The Component Framework may
-also use its own error handling also for errors resulting from request
-processing failures, for example if authentication is required or if the
-request URL cannot be resolved to a Content object.</p>
+<p>This specification does not define, how error handlers are configured and used if the Component Framework provides error handling support. Likewise the Component Framework may or may not implement support to handle calls to the <code>ComponentResponse.sendError</code> method. The Component Framework may also use its own error handling also for errors resulting from request processing failures, for example if authentication is required or if the request URL cannot be resolved to a Content object.</p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
- Rev. 1328899 by fmeschbe on Sun, 22 Apr 2012 16:52:13 +0000
+ Rev. 1341347 by fmeschbe on Tue, 22 May 2012 08:25:18 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project