incubator-sling-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r818658 [17/23] - in /websites/staging/sling/trunk/content: ./ tutorials-how-tos/
Date Tue, 22 May 2012 08:25:36 GMT
Modified: websites/staging/sling/trunk/content/request-parameters.html
==============================================================================
--- websites/staging/sling/trunk/content/request-parameters.html (original)
+++ websites/staging/sling/trunk/content/request-parameters.html Tue May 22 08:25:32 2012
@@ -82,126 +82,49 @@
         <a href="/">Home</a>
       </div>
       <h1>Request Parameters</h1>
-      <p><a name="RequestParameters-RequestParameterHandlinginSling"></a></p>
-<h1 id="request-parameter-handling-in-sling">Request Parameter Handling in Sling</h1>
-<p>{excerpt:hidden=true}Explains how Sling provides request parameters to the
-<em>Component</em>.{excerpt}</p>
-<p><a name="RequestParameters-ServletAPI"></a></p>
+      <h1 id="request-parameter-handling-in-sling">Request Parameter Handling in Sling</h1>
 <h2 id="servlet-api">Servlet API</h2>
-<p>The Servlet API specification provides the following methods to access the
-parameters of a request</p>
-<table>
-<tr><td> *HttpServletRequest.getQueryString()* </td><td> Returns the query part of the
-request URL </td></tr>
-<tr><td> *ServletRequest.getParameter(String)* </td><td> Returns the (first) named
-parameter </td></tr>
-<tr><td> *ServletRequest.getParameterValues(String)* </td><td> Returns all parameters of
-that name </td></tr>
-<tr><td> *ServletRequest.getParameterMap()* </td><td> Returns all parameters as a map of  </td></tr>
-<tr><td> *ServletRequest.getParameterNames()* </td><td> Returns an enumeration of the
-names of the parameters </td></tr>
-</table>
-
-<p>As a special restriction only two kinds of parameters are supported: (1)
-Query String parameters and (2) parameters contained in the request data of
-content type <em>application/x-www-form-encoded</em>. That is file uploads using
-request data of type <em>multipart/form-data</em> are not directly supported by
-the servlet specification. Finally the actual encoding of the parameters is
-all but safe because the encoding of URLs is not very well defined and
-browsers do not set the character encoding when sending post data.
-Fortunately, they use the same character encoding for sending back form
-content as was used by the server to send the form.</p>
-<p><a name="RequestParameters-SlingAPI"></a></p>
+<p>The Servlet API specification provides the following methods to access the parameters of a request</p>
+<p>| <code>HttpServletRequest.getQueryString()</code> | Returns the query part of the request URL |
+| <code>ServletRequest.getParameter(String)</code> | Returns the (first) named parameter |
+| <code>ServletRequest.getParameterValues(String)</code> | Returns all parameters of that name |
+| <code>ServletRequest.getParameterMap()</code> | Returns all parameters as a map of <code>String[]()</code> |
+| <code>ServletRequest.getParameterNames()</code> | Returns an enumeration of the names of the parameters |</p>
+<p>As a special restriction only two kinds of parameters are supported: (1) Query String parameters and (2) parameters contained in the request data of content type <code>application/x-www-form-encoded</code>. That is file uploads using request data of type <code>multipart/form-data</code> are not directly supported by the servlet specification. Finally the actual encoding of the parameters is all but safe because the encoding of URLs is not very well defined and browsers do not set the character encoding when sending post data. Fortunately, they use the same character encoding for sending back form content as was used by the server to send the form.</p>
 <h2 id="sling-api">Sling API</h2>
-<p>To overcome these restrictions and to provide uniform access to request
-parameters the Sling API in addition to the Servlet API methods to access
-parameters provides an abstraction of parameters which is applicable to all
-parameters sent by clients, the <em>RequestParameter</em> interface. Through
-this interface, each parameter may be analyzed for these topics:</p>
-<table>
-<tr><td> Raw Content </td><td> Byte array and *InputStream* representation of the
-request parameter values. You will generally use the *InputStream* to
-handle uploaded files. </td></tr>
-<tr><td> String Content </td><td> Access the values as strings is some given encoding (see
-below) or by requesting the conversion using an explicit encoding. </td></tr>
-<tr><td> File Uploads </td><td> Find out whether a parameter is a file upload, get the
-size in bytes of the parameter value and client side file name as sent by
-the browser. </td></tr>
-</table>
-
-<p>To accomodate this new interface as well as to provide easy access in the
-traditional way the <em>SlingHttpServletRequest</em> interface adds following
-methods to the standard Servlet API parameter access methods:</p>
-<table>
-<tr><td> *getRequestParameter(String)* </td><td> Returns the (first) named parameter as
-a *RequestParameter* instance </td></tr>
-<tr><td> *getRequestParameters(String)* </td><td> Returns the named parameter as an
-array of *RequestParameter* instances </td></tr>
-<tr><td> *getRequestParameterMap()* </td><td> Returns *RequestParameterMap* being a
-map of *RequestParameter* arrays indexed by parameter names </td></tr>
-</table>
-
-<p>All parameters are handled the same, that is all methods give access to the
-same parameters regardless of whether the parameters were transmitted in
-the request query, as part of form encoded data or as part of a
-<em>multipart/form-data</em> request.</p>
-<p>As of Sling Engine 2.1.0 the order or request parameters in the
-<em>getRequestParameterMap()</em>, <em>getParameterMap()</em>, and
-<em>getParameterNams()</em> is preserved as follows:</p>
+<p>To overcome these restrictions and to provide uniform access to request parameters the Sling API in addition to the Servlet API methods to access parameters provides an abstraction of parameters which is applicable to all parameters sent by clients, the <code>RequestParameter</code> interface. Through this interface, each parameter may be analyzed for these topics:</p>
+<p>| Raw Content | Byte array and <code>InputStream</code> representation of the request parameter values. You will generally use the <code>InputStream</code> to handle uploaded files. |
+| String Content | Access the values as strings is some given encoding (see below) or by requesting the conversion using an explicit encoding. |
+| File Uploads | Find out whether a parameter is a file upload, get the size in bytes of the parameter value and client side file name as sent by the browser. |</p>
+<p>To accomodate this new interface as well as to provide easy access in the traditional way the <code>SlingHttpServletRequest</code> interface adds following methods to the standard Servlet API parameter access methods:</p>
+<p>| <code>getRequestParameter(String)</code> | Returns the (first) named parameter as a <code>RequestParameter</code> instance |
+| <code>getRequestParameters(String)</code> | Returns the named parameter as an array of <code>RequestParameter</code> instances |
+| <code>getRequestParameterMap()</code> | Returns <code>RequestParameterMap</code> being a map of <code>RequestParameter</code> arrays indexed by parameter names |</p>
+<p>All parameters are handled the same, that is all methods give access to the same parameters regardless of whether the parameters were transmitted in the request query, as part of form encoded data or as part of a <code>multipart/form-data</code> request.</p>
+<p>As of Sling Engine 2.1.0 the order or request parameters in the <code>getRequestParameterMap()</code>, <code>getParameterMap()</code>, and <code>getParameterNams()</code> is preserved as follows:</p>
 <ul>
-<li>The first entries are the parameters reported by the servlet container.
-The order of these parameters amongst each other is not defined. The
-<em>SlingHttpServletRequest</em> provides them in the same order as provided by
-the servlet container.</li>
-<li>After the servlet container provided parameters are parameters extracted from the request in case <em>multipart/form-data</em> POST requests. The order of these parameters is preserved as they are submitted in the request. This conforms to HTML 4.01 spec on forms submitted with multipart/form-data encoding: <em>A "multipart/form-data" message contains a series of parts, each representing a successful control. The parts are sent to the processing agent in the same order the corresponding controls appear in the document stream. Part boundaries should not occur in any of the data; how this is done lies outside the scope of this specification</em> (<a href="http://www.w3.org/TR/html401/interact/forms.html">17.13.4 Form content types</a>
-)</li>
+<li>The first entries are the parameters reported by the servlet container. The order of these parameters amongst each other is not defined. The <code>SlingHttpServletRequest</code> provides them in the same order as provided by the servlet container.</li>
+<li>After the servlet container provided parameters are parameters extracted from the request in case <code>multipart/form-data</code> POST requests. The order of these parameters is preserved as they are submitted in the request. This conforms to HTML 4.01 spec on forms submitted with multipart/form-data encoding: <em>A "multipart/form-data" message contains a series of parts, each representing a successful control. The parts are sent to the processing agent in the same order the corresponding controls appear in the document stream. Part boundaries should not occur in any of the data; how this is done lies outside the scope of this specification</em> (<a href="">17.13.4 Form content types</a>)</li>
 </ul>
-<p>Be warned: Only rely on request parameter ordering <em>multipart/form-data</em>
-POST requests without a query part in the request URL.</p>
-<p><a name="RequestParameters-CharacterEncoding"></a></p>
+<p>Be warned: Only rely on request parameter ordering <code>multipart/form-data</code> POST requests without a query part in the request URL.</p>
 <h2 id="character-encoding">Character Encoding</h2>
-<p>Traditionally, the encoding of parameters, especially in text area input
-forms, has been a big issue. To solve this issue Sling introduces the
-following convention:</p>
+<p>Traditionally, the encoding of parameters, especially in text area input forms, has been a big issue. To solve this issue Sling introduces the following convention:</p>
 <ul>
-<li>All forms should contain a hidden field of the name <em>_charset_</em>
-containing the actual encoding used to send the form from the server to the
-client</li>
+<li>All forms should contain a hidden field of the name <code>\*charset\*</code> containing the actual encoding used to send the form from the server to the client</li>
 <li>All forms should be sent with <em>UTF-8</em> character encoding</li>
 </ul>
-<p>The first rule is essential as it helps decoding the form input correctly.
-The second rule is not actually a very hard requirement but to enable
-support for all (or most) character sets used, using <em>UTF-8</em> is one of the
-best choices anyway.</p>
-<p>When Sling is now receiving a request and is asked for the parameters, the
-parameters are parsed in two phases: The first phase just parses the raw
-input data using an identity transformation of bytes to characters. This
-identity transformation happens to generate strings as the original data
-was generated with <em>ISO-8859-1</em> encoding. The second phase locates the
-<em>_charset_</em> parameter and fixes the character encodings of the
-parameters as follows:</p>
+<p>The first rule is essential as it helps decoding the form input correctly. The second rule is not actually a very hard requirement but to enable support for all (or most) character sets used, using <em>UTF-8</em> is one of the best choices anyway.</p>
+<p>When Sling is now receiving a request and is asked for the parameters, the parameters are parsed in two phases: The first phase just parses the raw input data using an identity transformation of bytes to characters. This identity transformation happens to generate strings as the original data was generated with <code>ISO-8859-1</code> encoding. The second phase locates the <code>\*charset\*</code> parameter and fixes the character encodings of the parameters as follows:</p>
 <ul>
 <li>All names of the parameters are re-encoded</li>
-<li>The parameter values are re-encoded, unless the parameter value is an uploaded file. Actually the parameter (not the files of course) are internally as  where the conversion to a string is done on the fly (and yes, the
-conversion using the <em>_charset_</em> character encoding is of course cached
-for performance reasons)</li>
-<li>If the parameter is an uploaded file, the file name is re-encoded on
-the fly when accessed</li>
+<li>The parameter values are re-encoded, unless the parameter value is an uploaded file. Actually the parameter (not the files of course) are internally as <code>byte[]()</code> where the conversion to a string is done on the fly (and yes, the conversion using the <code>\*charset\*</code> character encoding is of course cached for performance reasons)</li>
+<li>If the parameter is an uploaded file, the file name is re-encoded on the fly when accessed</li>
 </ul>
 <p>{info}
-Up to and including Sling Engine 2.2.2 request parameters are always
-decoded with ISO-8859-1 encoding if the <em>_charset_</em> request parameter
-is missing. As of Sling Engine 2.2.4 the <em>_charset_</em> request parameter
-is optional. As of this version the Sling Main Servlet supports a
-configuration setting which allows to change the default character encoding
-used if the <em>_charset_</em> request parameter is missing. To enable this
-functionality set the <em>sling.default.parameter.encoding</em> parameter of the
-Sling Main Servlet (PID <em>org.apache.sling.engine.impl.SlingMainServlet</em>)
-configuration to the desired encoding, which of course must be supported by
-the actual Java Platform.
+Up to and including Sling Engine 2.2.2 request parameters are always decoded with ISO-8859-1 encoding if the <code>\*charset\*</code> request parameter is missing. As of Sling Engine 2.2.4 the <code>\*charset\*</code> request parameter is optional. As of this version the Sling Main Servlet supports a configuration setting which allows to change the default character encoding used if the <code>\*charset\*</code> request parameter is missing. To enable this functionality set the <code>sling.default.parameter.encoding</code> parameter of the Sling Main Servlet (PID <code>org.apache.sling.engine.impl.SlingMainServlet</code>) configuration to the desired encoding, which of course must be supported by the actual Java Platform.
 {info}</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/request-processing.html
==============================================================================
--- websites/staging/sling/trunk/content/request-processing.html (original)
+++ websites/staging/sling/trunk/content/request-processing.html Tue May 22 08:25:32 2012
@@ -82,237 +82,90 @@
         <a href="/">Home</a>
       </div>
       <h1>Request Processing</h1>
-      <p><a name="RequestProcessing-HTTPRequestProcessing"></a></p>
-<h1 id="http-request-processing">HTTP Request Processing</h1>
+      <h1 id="http-request-processing">HTTP Request Processing</h1>
 <p>{note:title=Page Status}
-2008-02-13: this page is <em>out of sync</em> with the current codebase, needs to
-be reviewed and updated.
+2008-02-13: this page is <em>out of sync</em> with the current codebase, needs to be reviewed and updated.
 {note}</p>
-<p>One of the core problems towards understanding how Sling works is knowing
-how a Client Request is processed by Sling. This page describes the flow of
-processing requests inside Sling.</p>
-<p><a name="RequestProcessing-CoreRequestProcessing"></a></p>
+<p>One of the core problems towards understanding how Sling works is knowing how a Client Request is processed by Sling. This page describes the flow of processing requests inside Sling.</p>
 <h2 id="core-request-processing">Core Request Processing</h2>
-<p>The HTTP request enters Sling in the
- method as the <em>ComponentRequestHandlerImpl</em>
-is registered as the Servlet handling HTTP requests. This method sets up
-the initial <em>ComponentRequest</em> and <em>ComponentResponse</em> objects and
-hands the request over to the first <em>ComponentFilterChain</em>. This first
-filter chain calls all <em>ComponentFilter</em> instances registered as request
-level filters. After processing all filters in the request level filter
-chain, the request is handed over to the second <em>ComponentFilterChain</em>
-which calls all <em>ComponentFilter</em> instances registered as component level
-filters. At the end of the second filter chain the <em>service</em> method of
-the actual <em>Component</em> to which the request resolved is called.</p>
-<p>As the component is now processing the request, it may decide to dispatch
-the request to some other content such as for example a paragraph system or
-navigation component. To do this, the component will call the
-<em>RequestDispatcher.include</em> method. If the request dispatcher dispatches
-to a <em>Content</em> object Sling will hand the dispatch request over to the
-component level filter chain, which at the end will call the <em>service</em>
-method for the <em>Content</em> object to dispatched to. This process may be
-repeated at the component's discretion only limited by processing resources
-such as available memory.</p>
-<p>As can be seen Sling itself is absed on the Component API
-<em>ComponentFilter</em> mechanism. As such Sling provides and uses the
-following filters in the Sling Core bundle:</p>
+<p>The HTTP request enters Sling in the <code>org.apache.sling.core.ComponentRequestHandlerImpl.service(ServletRequest req, ServletResponse res)</code> method as the <code>ComponentRequestHandlerImpl</code> is registered as the Servlet handling HTTP requests. This method sets up the initial <code>ComponentRequest</code> and <code>ComponentResponse</code> objects and hands the request over to the first <code>ComponentFilterChain</code>. This first filter chain calls all <code>ComponentFilter</code> instances registered as request level filters. After processing all filters in the request level filter chain, the request is handed over to the second <code>ComponentFilterChain</code> which calls all <code>ComponentFilter</code> instances registered as component level filters. At the end of the second filter chain the <code>service</code> method of the actual <code>Component</code> to which the request resolved is called.</p>
+<p>As the component is now processing the request, it may decide to dispatch the request to some other content such as for example a paragraph system or navigation component. To do this, the component will call the <code>RequestDispatcher.include</code> method. If the request dispatcher dispatches to a <code>Content</code> object Sling will hand the dispatch request over to the component level filter chain, which at the end will call the <code>service</code> method for the <code>Content</code> object to dispatched to. This process may be repeated at the component's discretion only limited by processing resources such as available memory.</p>
+<p>As can be seen Sling itself is absed on the Component API <code>ComponentFilter</code> mechanism. As such Sling provides and uses the following filters in the Sling Core bundle:</p>
 <p>{table:class=confluenceTable}
 {tr}{th:colspan=2|class=confluenceTh} Request Level Filters {th}{tr}
-{tr}{td:class=confluenceTd} <em>ErrorHandlerFilter</em>
-{td}{td:class=confluenceTd} Handles exceptions thrown while processing the
-request as well implements the <em>ComponentResponse.sendError()</em> method
-{td}{tr}
-{tr}{td:class=confluenceTd} <em>AuthenticationFilter</em>
-{td}{td:class=confluenceTd} Implements authentication for the request and
-provides the JCR Session of the request {td}{tr}
-{tr}{td:class=confluenceTd} <em>BurstCacheFilter</em>
-{td}{td:class=confluenceTd} Checks whether the request may be handled by
-cached response data {td}{tr}
-{tr}{td:class=confluenceTd} <em>LocaleResolverFilter</em>
-{td}{td:class=confluenceTd} Provides information on the <em>Locale</em> to be
-used for request processing. This filter implements the
-<em>ComponentRequest.getLocale()</em> method {td}{tr}
-{tr}{td:class=confluenceTd} <em>ThemeResolverFilter</em>
-{td}{td:class=confluenceTd} Provides the <em>Theme</em> for the request. The
-theme is provided as a request attribute {td}{tr}
-{tr}{td:class=confluenceTd} <em>URLMapperFilter</em> {td}{td:class=confluenceTd}
-Resolves the request URL to a JCR Node which may be mapped into a
-<em>Content</em> object {td}{tr}
-{tr}{td:class=confluenceTd} <em>ZipFilter</em> {td}{td:class=confluenceTd}
-Sample filter showing how the request response might be compressed
-according to the <em>Accept-Encoding</em> request header. This filter is not
-enabled by default. {td}{tr}
+{tr}{td:class=confluenceTd} <code>ErrorHandlerFilter</code> {td}{td:class=confluenceTd} Handles exceptions thrown while processing the request as well implements the <code>ComponentResponse.sendError()</code> method {td}{tr}
+{tr}{td:class=confluenceTd} <code>AuthenticationFilter</code> {td}{td:class=confluenceTd} Implements authentication for the request and provides the JCR Session of the request {td}{tr}
+{tr}{td:class=confluenceTd} <code>BurstCacheFilter</code> {td}{td:class=confluenceTd} Checks whether the request may be handled by cached response data {td}{tr}
+{tr}{td:class=confluenceTd} <code>LocaleResolverFilter</code> {td}{td:class=confluenceTd} Provides information on the <code>Locale</code> to be used for request processing. This filter implements the <code>ComponentRequest.getLocale()</code> method {td}{tr}
+{tr}{td:class=confluenceTd} <code>ThemeResolverFilter</code> {td}{td:class=confluenceTd} Provides the <code>Theme</code> for the request. The theme is provided as a request attribute {td}{tr}
+{tr}{td:class=confluenceTd} <code>URLMapperFilter</code> {td}{td:class=confluenceTd} Resolves the request URL to a JCR Node which may be mapped into a <code>Content</code> object {td}{tr}
+{tr}{td:class=confluenceTd} <code>ZipFilter</code> {td}{td:class=confluenceTd} Sample filter showing how the request response might be compressed according to the <em>Accept-Encoding</em> request header. This filter is not enabled by default. {td}{tr}
 {table}</p>
-<p>Deducing from these lists of filters, the actual request processing can be
-refined into the following steps:</p>
+<p>Deducing from these lists of filters, the actual request processing can be refined into the following steps:</p>
 <ol>
-<li>Extract user authentication information and acquire the JCR session to
-access content. If the request has no user authentication data the such
-data may be requested from the user (for example by sending a HTTP 401
-status) or an anonymous repository session might be acquired.</li>
-<li>Check whether the request may be handled by data stored in the cache.
-If the request is cacheable and a cache entry exists for the request URL,
-the request data is returned to the client and request processing may
-terminate. Otherwise request processing will continue and optionally ensure
-that any response data is entered into the cache. Of course, if the request
-is not cacheable, for example because there are request parameters, or if
-any of the <em>Component</em> instances called during request processing decide
-to signal non-cacheability for whatever reason, the response data will of
-course not cached.</li>
-<li>Extract the <em>java.util.Locale</em> from the request such that further
-processing may use properly translated messages. By default, the locale of
-the underlying Servlet request is used as the request locale. Other
-possibilities would be to use special cookies or some locale encoding in
-the path.</li>
-<li>Find the theme (or skin) to use to render the response. This step will
-add a <em>org.apache.sling.theme.Theme</em> object as a request parameter, which
-may be used by <em>Component</em>s to decide on specific rendering. For example,
-the theme may encapsulate information on the CSS to use for responses
-rendered as HTML.</li>
-<li>Resolve the request URL into a <em>Content</em> object.</li>
+<li>Extract user authentication information and acquire the JCR session to access content. If the request has no user authentication data the such data may be requested from the user (for example by sending a HTTP 401 status) or an anonymous repository session might be acquired.</li>
+<li>Check whether the request may be handled by data stored in the cache. If the request is cacheable and a cache entry exists for the request URL, the request data is returned to the client and request processing may terminate. Otherwise request processing will continue and optionally ensure that any response data is entered into the cache. Of course, if the request is not cacheable, for example because there are request parameters, or if any of the <code>Component</code> instances called during request processing decide to signal non-cacheability for whatever reason, the response data will of course not cached.</li>
+<li>Extract the <code>java.util.Locale</code> from the request such that further processing may use properly translated messages. By default, the locale of the underlying Servlet request is used as the request locale. Other possibilities would be to use special cookies or some locale encoding in the path.</li>
+<li>Find the theme (or skin) to use to render the response. This step will add a <code>org.apache.sling.theme.Theme</code> object as a request parameter, which may be used by <code>Component</code>s to decide on specific rendering. For example, the theme may encapsulate information on the CSS to use for responses rendered as HTML.</li>
+<li>Resolve the request URL into a <code>Content</code> object.</li>
 </ol>
-<p>The default request level filter chain setup ends with finding the
-<em>Content</em> object requested by the request URL. After having found this
-object, the request is handed over to the component level filter chain,
-which is concerned with handling filtering on a single <em>Content</em>
-instance. As such, the component level filter chain is used for each
-<em>Content</em> object which is to be serviced either on behalf of the HTTP
-request or on behalf of request dispatcher. Thus the component level filter
-chain will generally called multiple times during a single request.</p>
+<p>The default request level filter chain setup ends with finding the <code>Content</code> object requested by the request URL. After having found this object, the request is handed over to the component level filter chain, which is concerned with handling filtering on a single <code>Content</code> instance. As such, the component level filter chain is used for each <code>Content</code> object which is to be serviced either on behalf of the HTTP request or on behalf of request dispatcher. Thus the component level filter chain will generally called multiple times during a single request.</p>
 <p>{table:class=confluenceTable}
 {tr}{th:colspan=2|class=confluenceTh} Component Level Filters {th}{tr}
-{tr}{td:class=confluenceTd} <em>CacheFilter</em> {td}{td:class=confluenceTd}
-Checks whether the request to the current <em>Content</em> object may be handled
-by cached response data {td}{tr}
-{tr}{td:class=confluenceTd} <em>ComponentResolverFilter</em>
-{td}{td:class=confluenceTd} Resolves the component ID returned by the
-<em>Content.getComponentId()</em> method into a <em>Component</em> instances, which
-will be called to service the request {td}{tr}
+{tr}{td:class=confluenceTd} <code>CacheFilter</code> {td}{td:class=confluenceTd} Checks whether the request to the current <code>Content</code> object may be handled by cached response data {td}{tr}
+{tr}{td:class=confluenceTd} <code>ComponentResolverFilter</code> {td}{td:class=confluenceTd} Resolves the component ID returned by the <code>Content.getComponentId()</code> method into a <code>Component</code> instances, which will be called to service the request {td}{tr}
 {table}</p>
-<p>Again, deducing from the list of filters, the following steps are taking to
-service a given <em>Content</em> object:</p>
+<p>Again, deducing from the list of filters, the following steps are taking to service a given <code>Content</code> object:</p>
 <ol>
-<li>Check whether the <em>Content</em> object processing may be handled from
-the cache. Same as with request level cache handling, a cache entry may
-exist for a single <em>Content</em> instance depending on whether the request is
-cacheable at all and on whether a cache entry exists. If a cache entry
-exists and may be used, the response data is simply spooled into the
-response and component level processing terminates for the <em>Content</em>
-object. Otherwise processing continues and may optionally lead to a new
-cache entry for the <em>Content</em> object to be reused later.</li>
-<li>Resolve the component ID returned by the <em>Content.getComponentId()</em>
-method into a <em>Component</em> object. Of course it is an error, if the
-component ID cannot be mapped into a <em>Component</em> object.</li>
+<li>Check whether the <code>Content</code> object processing may be handled from the cache. Same as with request level cache handling, a cache entry may exist for a single <code>Content</code> instance depending on whether the request is cacheable at all and on whether a cache entry exists. If a cache entry exists and may be used, the response data is simply spooled into the response and component level processing terminates for the <code>Content</code> object. Otherwise processing continues and may optionally lead to a new cache entry for the <code>Content</code> object to be reused later.</li>
+<li>Resolve the component ID returned by the <code>Content.getComponentId()</code> method into a <code>Component</code> object. Of course it is an error, if the component ID cannot be mapped into a <code>Component</code> object.</li>
 </ol>
-<p>After resolving the <em>Component</em> object default component filter chain
-terminates and control is handed over to the <em>service</em> method of the
-<em>Component</em> object resolved in the last step. At the discretion of the
-component request dispatchers may now be acquired to render other
-<em>Content</em> objects. In this case the component level filter chain is
-simply kicked of again resulting in the <em>service</em> method of another
-<em>Component</em> being called. And so forth.</p>
-<p><a name="RequestProcessing-ResolvingContent"></a></p>
+<p>After resolving the <code>Component</code> object default component filter chain terminates and control is handed over to the <code>service</code> method of the <code>Component</code> object resolved in the last step. At the discretion of the component request dispatchers may now be acquired to render other <code>Content</code> objects. In this case the component level filter chain is simply kicked of again resulting in the <code>service</code> method of another <code>Component</code> being called. And so forth.</p>
 <h2 id="resolving-content">Resolving Content</h2>
-<p>As we have seen, the last step in the request level filter chain is the
-resolution of the request URL into a <em>Content</em> object. The URL Mapper
-Filter implementing this resolution uses an instance of the
-<em>org.apache.sling.content.ContentMapper</em> interface which is acquired by
-calling the <em>org.apache.sling.content.jcr.JcrContentManagerFactory</em> with
-the repository session acquired by the authentication filter.</p>
-<p>The URL Mapper filter then tries to apply fixed mappings from request URL
-to destination paths to support shortcut URLs. For example the root path
-<em>/</em> may be mapped into the default landing page at <em>/default/home</em>. The
-list of such mappings is configurable through the Configuration Admin
-Service.</p>
-<p>Next the URL Mapper tries to apply prefix matching patterns. A list of
-patterns is iterated checking whether the prefix applies and, if so,
-replacing the prefix with another prefix and trying to resolve the result.
-This functionality enables relocation of a subtree of the repository. For
-example, all requests whose prefix is <em>/here</em> might be remapped with the
-new prefix <em>/content/there</em>. The result  of this remapping is then
-resolved.</p>
-<p>Resolution (currently) takes place on the last path segment of the request
-URL containing at least one dot. Parts of that segment are cut off after
-dots until no more dots exist in the URL. For each resulting substring, the
-<em>ContentManager.load(String)</em> method is called. This processing
-terminates if a <em>Content</em> object is found or if there is nothing to cut
-off any more.</p>
-<p>This resolution is very simple and straight forwards. Future development
-may add support for the following features:</p>
+<p>As we have seen, the last step in the request level filter chain is the resolution of the request URL into a <code>Content</code> object. The URL Mapper Filter implementing this resolution uses an instance of the <code>org.apache.sling.content.ContentMapper</code> interface which is acquired by calling the <code>org.apache.sling.content.jcr.JcrContentManagerFactory</code> with the repository session acquired by the authentication filter.</p>
+<p>The URL Mapper filter then tries to apply fixed mappings from request URL to destination paths to support shortcut URLs. For example the root path <code>/</code> may be mapped into the default landing page at <code>/default/home</code>. The list of such mappings is configurable through the Configuration Admin Service.</p>
+<p>Next the URL Mapper tries to apply prefix matching patterns. A list of patterns is iterated checking whether the prefix applies and, if so, replacing the prefix with another prefix and trying to resolve the result. This functionality enables relocation of a subtree of the repository. For example, all requests whose prefix is <code>/here</code> might be remapped with the new prefix <code>/content/there</code>. The result  of this remapping is then resolved.</p>
+<p>Resolution (currently) takes place on the last path segment of the request URL containing at least one dot. Parts of that segment are cut off after dots until no more dots exist in the URL. For each resulting substring, the <code>ContentManager.load(String)</code> method is called. This processing terminates if a <code>Content</code> object is found or if there is nothing to cut off any more.</p>
+<p>This resolution is very simple and straight forwards. Future development may add support for the following features:</p>
 <ul>
-<li><em>Vanity URLs</em> - Map the request URL according to the <em>Host</em> request
-header.</li>
-<li><em>Dynamic Mapping</em> - Add support for a set of variables in path and/or
-prefix mapping. For example, a prefix mapping  may contain the string
-<em>/content/${lang}/${user</em>} resulting in resolving a prefix according to
-the language of the current locale and the name of the authenticated used.</li>
+<li><em>Vanity URLs</em> - Map the request URL according to the <code>Host</code> request header.</li>
+<li><em>Dynamic Mapping</em> - Add support for a set of variables in path and/or prefix mapping. For example, a prefix mapping  may contain the string <code>/content/$\{lang}/$\{user</code>} resulting in resolving a prefix according to the language of the current locale and the name of the authenticated used.</li>
 </ul>
-<p><a name="RequestProcessing-RegisteringComponents"></a></p>
 <h2 id="registering-components">Registering Components</h2>
-<p>The last step of the component level filter chain is resolving the
-<em>Component</em> from the component ID of the <em>Content</em> object. Sling
-implements this resolution by making use of the OSGi service registry. That
-is, each component is to be registered as a service with the name
-<em>org.apache.sling.component.Component</em>. The <em>ComponentResolverFilter</em>
-is listening for these components and registers them internally in a map
-indexed by the IDs of the component as returned by the
-<em>Component.getId()</em> method.</p>
-<p>When a component has to be resolved, the component ID returned by the
-<em>Content</em> object is simply looked up in the component map. If found, that
-component is used. Otherwise a fall back algorithm is applied which is
-described on the <a href="default-mapping-and-rendering.html">Default Content Mapping and Request Rendering</a>
- page.</p>
-<p><a name="RequestProcessing-ReqisteringFilters"></a></p>
+<p>The last step of the component level filter chain is resolving the <code>Component</code> from the component ID of the <code>Content</code> object. Sling implements this resolution by making use of the OSGi service registry. That is, each component is to be registered as a service with the name <code>org.apache.sling.component.Component</code>. The <code>ComponentResolverFilter</code> is listening for these components and registers them internally in a map indexed by the IDs of the component as returned by the <code>Component.getId()</code> method.</p>
+<p>When a component has to be resolved, the component ID returned by the <code>Content</code> object is simply looked up in the component map. If found, that component is used. Otherwise a fall back algorithm is applied which is described on the <a href="/default-mapping-and-rendering.html">Default Content Mapping and Request Rendering</a> page.</p>
 <h2 id="reqistering-filters">Reqistering Filters</h2>
-<p>Just as <em>Component</em> instances used by Sling are expected to be registered
-as OSGi services, the <em>ComponentFilter</em>s to be 
-used have to be registered as services under the name
-<em>org.apache.sling.component.ComponentFilter</em>. Sling picks up all
-registered component filters and adds them to the respective filter chains.</p>
-<p>Service properties set upon registration of the filter define the chain to
-which the filter belongs and the order in which the filters should be
-processed:</p>
+<p>Just as <code>Component</code> instances used by Sling are expected to be registered as OSGi services, the <code>ComponentFilter</code>s to be 
+used have to be registered as services under the name <code>org.apache.sling.component.ComponentFilter</code>. Sling picks up all registered component filters and adds them to the respective filter chains.</p>
+<p>Service properties set upon registration of the filter define the chain to which the filter belongs and the order in which the filters should be processed:</p>
 <table>
-<tr><th> Property </th><th> Description </th></tr>
-<tr><td> *filter.scope* </td><td> Defines the chain to which the filter is added.
-Supported values are *component* for component level filters and
-*request* for request level filters. If this property is missing or set
-to an unknown value the filter is added to the request level filter chain.
-</td></tr>
-<tr><td> *filter.order* </td><td> Defines the weight of the filter to resolve the
-processing order. This property must be an *java.lang.Integer*. If not
-set or not an *Integer* the order defaults to *Integer.MAX_VALUE*. The
-lower the order number the earlier in the filter chain will the filter be
-inserted. If two filters are registered with the same order value, the
-filter with the lower *service.id* value is called first. </td></tr>
+<thead>
+<tr>
+<th>Property</th>
+<th>Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td><code>filter.scope</code></td>
+<td>Defines the chain to which the filter is added. Supported values are <code>component</code> for component level filters and <code>request</code> for request level filters. If this property is missing or set to an unknown value the filter is added to the request level filter chain.</td>
+</tr>
+<tr>
+<td><code>filter.order</code></td>
+<td>Defines the weight of the filter to resolve the processing order. This property must be an <code>java.lang.Integer</code>. If not set or not an <code>Integer</code> the order defaults to <code>Integer.MAX_VALUE</code>. The lower the order number the earlier in the filter chain will the filter be inserted. If two filters are registered with the same order value, the filter with the lower <code>service.id</code> value is called first.</td>
+</tr>
+</tbody>
 </table>
-
-<p><a name="RequestProcessing-ContentisaJavaObject"></a></p>
 <h2 id="content-is-a-java-object">Content is a Java Object</h2>
-<p>It is crucial to understand that <em>Content</em> is an interface and the
-request processor of Sling does not actually care, how the <em>Content</em>
-instance comes to live as long as the is such an object and there is a
-<em>Component</em> instance capable of servicing the <em>Content</em> object.</p>
-<p>By default Sling uses the <em>URL Mapper</em> to resolve the request URL into a
-<em>Content</em> object. When a <em>Component</em> is tasked with servicing a
-<em>Content</em> object it usually uses the <em>ComponentRequestDispatcher</em> to
-ask Sling to service another content object generally identified by a
-(relative or absolute) path to a JCR Repository Node from which the
-<em>Content</em> object is loaded.</p>
-<p>But instead of having Sling resolve a path into a <em>Content</em> object the
-component may just as well create a <em>Content</em> object and hand it over to
-the <em>ComponentRequestDispatcher</em> for service. Consider a request which is
-handled by a <em>PageComponent</em>. This component has to draw a navigation
-tree somewhere in the response. So the component could of course insist on
-having a <em>navigation</em> child node to dispatch rendering to as follows:</p>
+<p>It is crucial to understand that <code>Content</code> is an interface and the request processor of Sling does not actually care, how the <code>Content</code> instance comes to live as long as the is such an object and there is a <code>Component</code> instance capable of servicing the <code>Content</code> object.</p>
+<p>By default Sling uses the <em>URL Mapper</em> to resolve the request URL into a <code>Content</code> object. When a <code>Component</code> is tasked with servicing a <code>Content</code> object it usually uses the <code>ComponentRequestDispatcher</code> to ask Sling to service another content object generally identified by a (relative or absolute) path to a JCR Repository Node from which the <code>Content</code> object is loaded.</p>
+<p>But instead of having Sling resolve a path into a <code>Content</code> object the component may just as well create a <code>Content</code> object and hand it over to the <code>ComponentRequestDispatcher</code> for service. Consider a request which is handled by a <code>PageComponent</code>. This component has to draw a navigation tree somewhere in the response. So the component could of course insist on having a <code>navigation</code> child node to dispatch rendering to as follows:</p>
 <div class="codehilite"><pre><span class="n">RequestDispatcher</span> <span class="n">rd</span> <span class="o">=</span> <span class="n">request</span><span class="o">.</span><span class="n">getRequestDispatcher</span><span class="p">(</span><span class="s">&quot;navigation&quot;</span><span class="p">);</span>
 <span class="n">rd</span><span class="o">.</span><span class="n">include</span><span class="p">(</span><span class="n">request</span><span class="p">,</span> <span class="n">response</span><span class="p">);</span>
 </pre></div>
 
 
-<p>What happens, though, if there is no <em>navigation</em> child node ? Probably,
-the request will fail with some error status. Of course the component could
-be more clever and do:</p>
+<p>What happens, though, if there is no <code>navigation</code> child node ? Probably, the request will fail with some error status. Of course the component could be more clever and do:</p>
 <div class="codehilite"><pre><span class="n">Content</span> <span class="n">navigation</span> <span class="o">=</span> <span class="n">request</span><span class="o">.</span><span class="n">getContent</span><span class="p">(</span><span class="s">&quot;navigation&quot;</span><span class="p">);</span>
 <span class="k">if</span> <span class="p">(</span><span class="n">navigation</span> <span class="o">!=</span> <span class="n">null</span><span class="p">)</span> <span class="p">{</span>
     <span class="n">RequestDispatcher</span> <span class="n">rd</span> <span class="o">=</span> <span class="n">request</span><span class="o">.</span><span class="n">getRequestDispatcher</span><span class="p">(</span><span class="n">navigation</span><span class="p">);</span>
@@ -321,16 +174,13 @@ be more clever and do:</p>
 </pre></div>
 
 
-<p>Still, if the <em>navigation</em> child node does not exist, there is no
-navigation drawn; at least there will be now error. Since Sling does not
-actually care, how a <em>Content</em> object comes to live, the component could
-do the following:</p>
+<p>Still, if the <code>navigation</code> child node does not exist, there is no navigation drawn; at least there will be now error. Since Sling does not actually care, how a <code>Content</code> object comes to live, the component could do the following:</p>
 <div class="codehilite"><pre><span class="n">Content</span> <span class="n">navigation</span> <span class="o">=</span> <span class="k">new</span> <span class="n">Content</span><span class="p">()</span> <span class="p">{</span>
     <span class="n">public</span> <span class="n">String</span> <span class="n">getPath</span><span class="p">()</span> <span class="p">{</span>
-    <span class="k">return</span> <span class="n">request</span><span class="o">.</span><span class="n">getContent</span><span class="p">()</span><span class="o">.</span><span class="n">getPath</span><span class="p">()</span> <span class="o">+</span> <span class="s">&quot;/navigation&quot;</span><span class="p">;</span>
+        <span class="k">return</span> <span class="n">request</span><span class="o">.</span><span class="n">getContent</span><span class="p">()</span><span class="o">.</span><span class="n">getPath</span><span class="p">()</span> <span class="o">+</span> <span class="s">&quot;/navigation&quot;</span><span class="p">;</span>
     <span class="p">}</span>
     <span class="n">public</span> <span class="n">String</span> <span class="n">getComponentId</span><span class="p">()</span> <span class="p">{</span>
-    <span class="k">return</span> <span class="n">NavigationComponent</span><span class="o">.</span><span class="n">getClass</span><span class="p">()</span><span class="o">.</span><span class="n">getName</span><span class="p">();</span>
+        <span class="k">return</span> <span class="n">NavigationComponent</span><span class="o">.</span><span class="n">getClass</span><span class="p">()</span><span class="o">.</span><span class="n">getName</span><span class="p">();</span>
     <span class="p">}</span>
 <span class="p">}</span>
 
@@ -339,20 +189,17 @@ do the following:</p>
 </pre></div>
 
 
-<p>Of course, the page component now has to have knowledge about the actual
-<em>Component</em> to use.</p>
-<p>Finally, as a further enhancement, the Component might even decide to first
-check for a <em>navigation</em> child node. If such a node does not exist the
-navigation <em>Content</em> object is just created:</p>
+<p>Of course, the page component now has to have knowledge about the actual <code>Component</code> to use.</p>
+<p>Finally, as a further enhancement, the Component might even decide to first check for a <code>navigation</code> child node. If such a node does not exist the navigation <code>Content</code> object is just created:</p>
 <div class="codehilite"><pre><span class="n">Content</span> <span class="n">navigation</span> <span class="o">=</span> <span class="n">request</span><span class="o">.</span><span class="n">getContent</span><span class="p">(</span><span class="s">&quot;navigation&quot;</span><span class="p">);</span>
 <span class="k">if</span> <span class="p">(</span><span class="n">navigation</span> <span class="o">==</span> <span class="n">null</span><span class="p">)</span> <span class="p">{</span>
     <span class="n">navigation</span> <span class="o">=</span> <span class="k">new</span> <span class="n">Content</span><span class="p">()</span> <span class="p">{</span>
-    <span class="n">public</span> <span class="n">String</span> <span class="n">getPath</span><span class="p">()</span> <span class="p">{</span>
-        <span class="k">return</span> <span class="n">request</span><span class="o">.</span><span class="n">getContent</span><span class="p">()</span><span class="o">.</span><span class="n">getPath</span><span class="p">()</span> <span class="o">+</span> <span class="s">&quot;/navigation&quot;</span><span class="p">;</span>
-    <span class="p">}</span>
-    <span class="n">public</span> <span class="n">String</span> <span class="n">getComponentId</span><span class="p">()</span> <span class="p">{</span>
-        <span class="k">return</span> <span class="n">NavigationComponent</span><span class="o">.</span><span class="n">getClass</span><span class="p">()</span><span class="o">.</span><span class="n">getName</span><span class="p">();</span>
-    <span class="p">}</span>
+        <span class="n">public</span> <span class="n">String</span> <span class="n">getPath</span><span class="p">()</span> <span class="p">{</span>
+            <span class="k">return</span> <span class="n">request</span><span class="o">.</span><span class="n">getContent</span><span class="p">()</span><span class="o">.</span><span class="n">getPath</span><span class="p">()</span> <span class="o">+</span> <span class="s">&quot;/navigation&quot;</span><span class="p">;</span>
+        <span class="p">}</span>
+        <span class="n">public</span> <span class="n">String</span> <span class="n">getComponentId</span><span class="p">()</span> <span class="p">{</span>
+            <span class="k">return</span> <span class="n">NavigationComponent</span><span class="o">.</span><span class="n">getClass</span><span class="p">()</span><span class="o">.</span><span class="n">getName</span><span class="p">();</span>
+        <span class="p">}</span>
     <span class="p">}</span>
 <span class="p">}</span>
 
@@ -361,11 +208,9 @@ navigation <em>Content</em> object is ju
 </pre></div>
 
 
-<p>This could for example be used to fall back to a default navigation setup
-while providing for specialized navigation configuration in an optional
-<em>navigation</em> child node.</p>
+<p>This could for example be used to fall back to a default navigation setup while providing for specialized navigation configuration in an optional <code>navigation</code> child node.</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/resources.html
==============================================================================
--- websites/staging/sling/trunk/content/resources.html (original)
+++ websites/staging/sling/trunk/content/resources.html Tue May 22 08:25:32 2012
@@ -82,183 +82,83 @@
         <a href="/">Home</a>
       </div>
       <h1>Resources</h1>
-      <p><a name="Resources-Resources"></a></p>
-<h1 id="resources">Resources</h1>
-<p>{toc:minLevel=2}</p>
-<p><a name="Resources-WhatisaResource"></a></p>
+      <h1 id="resources">Resources</h1>
+<div class="toc">
+<ul>
+<li><a href="#resources">Resources</a><ul>
+<li><a href="#what-is-a-resource">What is a Resource</a></li>
+<li><a href="#how-to-get-a-resource">How to get a Resource</a><ul>
+<li><a href="#absolute-path-mapping">Absolute Path Mapping</a></li>
+<li><a href="#relative-path-resolution">Relative Path Resolution</a></li>
+<li><a href="#querying-resources">Querying Resources</a></li>
+</ul>
+</li>
+<li><a href="#providing-resources">Providing Resources</a><ul>
+<li><a href="#jcr-based-resources">JCR-based Resources</a></li>
+<li><a href="#bundle-based-resources">Bundle-based Resources</a></li>
+<li><a href="#servlet-resources">Servlet Resources</a></li>
+<li><a href="#file-system-resources">File System Resources</a></li>
+</ul>
+</li>
+<li><a href="#wrapdecorate-resources">Wrap/Decorate Resources</a></li>
+</ul>
+</li>
+</ul>
+</div>
 <h2 id="what-is-a-resource">What is a Resource</h2>
-<p>The Resource is one of the central parts of Sling. Extending from JCR's
-<em>Everything is Content</em>, Sling assumes <em>Everthing is a Resource</em>. Thus
-Sling is maintaining a virtual tree of resources, which is a merger of the
-actual contents in the JCR Repository and resources provided by so called
-resource providers. By doing this Sling fits very well in the paradigma of
-the REST architecture.</p>
-<p><a name="Resources-HowtogetaResource"></a></p>
+<p>The Resource is one of the central parts of Sling. Extending from JCR's <em>Everything is Content</em>, Sling assumes <em>Everthing is a Resource</em>. Thus Sling is maintaining a virtual tree of resources, which is a merger of the actual contents in the JCR Repository and resources provided by so called resource providers. By doing this Sling fits very well in the paradigma of the REST architecture.</p>
 <h2 id="how-to-get-a-resource">How to get a Resource</h2>
-<p>To get at Resources, you need a <em>ResourceResolver</em>. This interface
-defines four kinds of methods to access resources:
-<em> Absolute Path Mapping Resource Resolution: The
-</em>resolve(HttpServletRequest, String)<em> and </em>resolve(String)<em> methods are
-called to apply some implementation specific path matching algorithm to
-find a Resource. These methods are mainly used to map external paths - such
-as path components of request URLs - to Resources. To support creating
-external paths usable in an URL a third method </em>map(String)<em> is defined,
-which allows for round-tripping.
-</em> Absolute or Relative Path Resolution (including search path): The
-<em>getResource(String path)</em> and  methods may be used to access a resource with an absolute path
-directly. If it can't be found the path is assumed to be relative and the
-search path retrieved from <em>getSearchPath()</em> is used to retrieve the
-resource. This mechanism is similar to resolving a programm with the
-<em>PATH</em> environment variable in your favourite operating system.
-<em> Resource Enumeration: To enumerate resources and thus iterate the
-resource tree, the </em>listChildren(Resource)<em> method may be used. This
-method returns an </em>Iterator<Resource><em> listing all resources whose path
-prefix is the path of the given Resource. This method will of course also
-cross boundaries of registered </em>ResourceProvider<em> instances to enable
-iterating the complete resource tree.
-</em> Resource Querying: Querying resources is currently only supported for JCR
-Resources through the <em>findResources(String query, String language)</em> and
-<em>queryResources(String query, String language)</em> methods. For more
-information see the section on <a href="#querying_resources.html">Querying_Resources</a>
- below.</p>
-<p><a name="Resources-AbsolutePathMapping"></a></p>
+<p>To get at Resources, you need a <code>ResourceResolver</code>. This interface defines four kinds of methods to access resources:
+<em> Absolute Path Mapping Resource Resolution: The <code>resolve(HttpServletRequest, String)</code> and <code>resolve(String)</code> methods are called to apply some implementation specific path matching algorithm to find a Resource. These methods are mainly used to map external paths - such as path components of request URLs - to Resources. To support creating external paths usable in an URL a third method <code>map(String)</code> is defined, which allows for round-tripping.
+</em> Absolute or Relative Path Resolution (including search path): The <code>getResource(String path)</code> and <code>getResource(Resource base, String path)</code> methods may be used to access a resource with an absolute path directly. If it can't be found the path is assumed to be relative and the search path retrieved from <code>getSearchPath()</code> is used to retrieve the resource. This mechanism is similar to resolving a programm with the <code>PATH</code> environment variable in your favourite operating system.
+<em> Resource Enumeration: To enumerate resources and thus iterate the resource tree, the <code>listChildren(Resource)</code> method may be used. This method returns an <code>Iterator&lt;Resource&gt;</code> listing all resources whose path prefix is the path of the given Resource. This method will of course also cross boundaries of registered <code>ResourceProvider</code> instances to enable iterating the complete resource tree.
+</em> Resource Querying: Querying resources is currently only supported for JCR Resources through the <code>findResources(String query, String language)</code> and <code>queryResources(String query, String language)</code> methods. For more information see the section on <a href="">Querying*Resources</a> below.</p>
 <h3 id="absolute-path-mapping">Absolute Path Mapping</h3>
-<p>As has been said, the absolute path mapping methods
-<em>resolve(HttpServletRequest, String)</em> and <em>resolve(String)</em> apply some
-implementation specific path matching algorithm to find a Resource. The
-difference between the two methods is that the former may take more
-properties of the <em>HttpServletRequest</em> into account when resolving the
-Resoure, while the latter just has an absolute path to work on.</p>
+<p>As has been said, the absolute path mapping methods <code>resolve(HttpServletRequest, String)</code> and <code>resolve(String)</code> apply some implementation specific path matching algorithm to find a Resource. The difference between the two methods is that the former may take more properties of the <code>HttpServletRequest</code> into account when resolving the Resoure, while the latter just has an absolute path to work on.</p>
 <p>The general algorithm of the two methods is as follows:
-1. Call <em>HttpServletRequest.getScheme(), .getServerName(), getServerPort</em> to get an absolute path out of the request URL: [scheme](scheme.html)
-/[host].[port][path] (<em>resolve(HttpServletRequest, String)</em> method
-only, which)
-1. Check whether any virtual path matches the absolute path. If such a match
-exists, the next step is entered with the match.
-1. Apply a list of mappings in order to create a mapped path. The first
-mapped path resolving to a Resource is assumed success and the Resource
-found is returned.
-1. If no mapping created a mapped path addressing an existing Resource, the
-method fails and returns:</p>
+1. Call <code>HttpServletRequest.getScheme(), .getServerName(), getServerPort</code> to get an absolute path out of the request URL: [scheme]()/[host].[port][path] (<code>resolve(HttpServletRequest, String)</code> method only, which)
+1. Check whether any virtual path matches the absolute path. If such a match exists, the next step is entered with the match.
+1. Apply a list of mappings in order to create a mapped path. The first mapped path resolving to a Resource is assumed success and the Resource found is returned.
+1. If no mapping created a mapped path addressing an existing Resource, the method fails and returns:</p>
 <ul>
-<li>The <em>resolve(String)</em> and <em>resolve(HttpServletRequest,String)</em>
-methods return a <em>NonExistingResource</em></li>
-<li>The <em>getResource(String path)</em> and  methods return null</li>
+<li>The <code>resolve(String)</code> and <code>resolve(HttpServletRequest,String)</code> methods return a <code>NonExistingResource</code></li>
+<li>The <code>getResource(String path)</code> and <code>getResource(Resource base, String path)</code> methods return null</li>
 </ul>
-<p>The virtual path mapping may be used to create shortcut URLs for otherwise
-long and complicated URLs. An example of such an URL might be the main
-administrative page of a CMS system. So, administrators may access the root
-of the web application and directed to the main administrative page.</p>
-<p>The path mapping functionality may be used to hide internal resource
-organization from the request URL space. For example to better control the
-structure of your repository, you might decide to store all accessible data
-inside a <em>/content</em> subtree. To hide this fact from the users, a mapping
-may be defined to prefix all incoming paths with <em>/content</em> to get at the
-actual Resource.</p>
-<p>The <em>map(String)</em> applies the path mapping algorithm in the reverse
-order. That is, first the path mappings are reversed and then any virtual
-mappings are checked. So, a path <em>/content/sample</em> might be mapped
-<em>/sample</em> to revers the <em>/content</em> prefixing. Or the main
-administrative page - say <em>/system/admin/main.html</em> - may be mapped to
-the virtual URL <em>/</em>.</p>
-<p><a name="Resources-RelativePathResolution"></a></p>
+<p>The virtual path mapping may be used to create shortcut URLs for otherwise long and complicated URLs. An example of such an URL might be the main administrative page of a CMS system. So, administrators may access the root of the web application and directed to the main administrative page.</p>
+<p>The path mapping functionality may be used to hide internal resource organization from the request URL space. For example to better control the structure of your repository, you might decide to store all accessible data inside a <code>/content</code> subtree. To hide this fact from the users, a mapping may be defined to prefix all incoming paths with <code>/content</code> to get at the actual Resource.</p>
+<p>The <code>map(String)</code> applies the path mapping algorithm in the reverse order. That is, first the path mappings are reversed and then any virtual mappings are checked. So, a path <code>/content/sample</code> might be mapped <code>/sample</code> to revers the <code>/content</code> prefixing. Or the main administrative page - say <code>/system/admin/main.html</code> - may be mapped to the virtual URL <code>/</code>.</p>
 <h3 id="relative-path-resolution">Relative Path Resolution</h3>
-<p>Sometimes it is required to resolve relative paths to Resources. An example
-of such a use case is Script and Servlet resolution which starts with a
-relative path consisting of the Resource type, optional selectors and the
-request extension or method name. By scanning a search path for these
-relative paths a system provided Resource may be overwritten with some user
-defined implementation.</p>
-<p>Consider for example, the system would provide a Servlet to render Resources of type <em>nt:file</em>. This Servlet would be registered under the path <em>/libs/nt/file/html</em>. For a certain web application, this default HTML rendering might not be appropriate, so a Script is created as <em>/apps/nt/file/html.jsp</em> with a customized HTML rendering. By defining the search path to be <em>[</em> <em><em>/apps{</em>}{</em>}<em>,</em> <em><em>/libs{</em></em>} <em>](</em>-<em><em>/apps{</em>}{</em>}<em>,</em>-<em><em>/libs{</em></em>}-<em>.html)
-</em> the Servlet resolver would call the
-<em>ResourceResolver.getResource(String)</em> method with the relative path
-<em>nt/file/html</em> and be provided with the first matching resource -
-<em>/apps/nt/file/html.jsp</em> in this example.</p>
+<p>Sometimes it is required to resolve relative paths to Resources. An example of such a use case is Script and Servlet resolution which starts with a relative path consisting of the Resource type, optional selectors and the request extension or method name. By scanning a search path for these relative paths a system provided Resource may be overwritten with some user defined implementation.</p>
+<p>Consider for example, the system would provide a Servlet to render Resources of type <code>nt:file</code>. This Servlet would be registered under the path <code>/libs/nt/file/html</code>. For a certain web application, this default HTML rendering might not be appropriate, so a Script is created as <code>/apps/nt/file/html.jsp</code> with a customized HTML rendering. By defining the search path to be <em>[</em> <code>*/apps{*}{</code>}<em>,</em> <code>*/libs{*</code>} <em>]()</em> the Servlet resolver would call the <code>ResourceResolver.getResource(String)</code> method with the relative path <code>nt/file/html</code> and be provided with the first matching resource - <code>/apps/nt/file/html.jsp</code> in this example.</p>
 <p>Of course the search path is not used for absolute path arguments.</p>
-<p><a name="Resources-QueryingResources"></a></p>
 <h3 id="querying-resources">Querying Resources</h3>
-<p>For convenience the <em>ResourceResolver</em> provides two Resource querying
-methods <em>findResources</em> and <em>queryResources</em> both methods take as
-arguments a JCR query string and a query language name. These parameters
-match the parameter definition of the  method of the JCR API.</p>
+<p>For convenience the <code>ResourceResolver</code> provides two Resource querying methods <code>findResources</code> and <code>queryResources</code> both methods take as arguments a JCR query string and a query language name. These parameters match the parameter definition of the <code>QueryManager.createQuery(String statement, String language)</code> method of the JCR API.</p>
 <p>The return value of these two methods differ in the use case:
-<em> </em>findResources<em> returns an </em>Iteratory<Resource><em> of all Resources
-matching the query. This method is comparable to calling </em>getNodes()<em> on
-the </em>QueryResult<em> returned from executing the JCR query.
-</em> <em>queryResources</em> returns an <em>Iterator<Map<String, Object>&gt;</em>. Each
-entry in the iterator is a <em>Map&lt;String, Object</em> representing a JCR result
-<em>Row</em> in the <em>RowIterator</em> returned from executing the JCR query. The
-map is indexed by the column name and the value of each entry is the value
-of the named column as a Java Object.</p>
-<p>These methods are convenience methods to more easily post queries to the
-repository and to handle results in very straight forward way using only
-standard Java functionality.</p>
-<p>Please note, that Resource querying is currently only supported for
-repository based Resources. These query methods are not reflected in the
-<em>ResourceProvider</em> interface used to inject non-repository Resources into
-the Resource tree.</p>
-<p><a name="Resources-ProvidingResources"></a></p>
+<em> <code>findResources</code> returns an <code>Iteratory&lt;Resource&gt;</code> of all Resources matching the query. This method is comparable to calling <code>getNodes()</code> on the <code>QueryResult</code> returned from executing the JCR query.
+</em> <code>queryResources</code> returns an <code>Iterator&lt;Map&lt;String, Object&gt;&gt;</code>. Each entry in the iterator is a <code>Map&lt;String, Object</code> representing a JCR result <code>Row</code> in the <code>RowIterator</code> returned from executing the JCR query. The map is indexed by the column name and the value of each entry is the value of the named column as a Java Object.</p>
+<p>These methods are convenience methods to more easily post queries to the repository and to handle results in very straight forward way using only standard Java functionality.</p>
+<p>Please note, that Resource querying is currently only supported for repository based Resources. These query methods are not reflected in the <code>ResourceProvider</code> interface used to inject non-repository Resources into the Resource tree.</p>
 <h2 id="providing-resources">Providing Resources</h2>
-<p>The virtual Resource tree to which the the Resource accessor methods
-<em>resolve</em> and <em>getResource</em> provide access is implemented by a
-collection of registered <em>ResourceProvider</em> instances. The main Resource
-provider is of course the repository based <em>JcrResourceProvider</em> which
-supports Node and Property based resources. This Resource provider is
-always available in Sling. Further Resource providers may or may not exist.</p>
-<p>Each Resource provider is registered as an OSGi service with a required
-service registration property <em>provider.roots</em>. This is a multi-value
-String property listing the absolute paths Resource tree entries serving as
-roots to provided subtrees. For example, if a Resource provider is
-registered with the service registration property <em>provider.roots</em> set to
-<em>/some/root</em>, all paths starting with <em>/some/root</em> are first looked up in
-the given Resource Provider.</p>
-<p>When looking up a Resource in the registered Resource providers, the
-<em>ResourceResolver</em> applies a longest prefix matching algorithm to find
-the best match. For example consider three Resource provider registered as
-follows:
-<em> JCR Resource provider as </em>/<em>
-</em> Resource provider R1 as <em>/some</em>
-<em> Resource provider R2 as </em>/some/path*</p>
-<p>When accessing a Resource with path <em>/some/path/resource</em> the Resource
-provider <em>R2</em> is first asked. If that cannot provide the resource, Resource
-provider <em>R1</em> is asked and finally the JCR Resource provider is asked. The
-first Resource provider having a Resource with the requested path will be
-used.</p>
-<p><a name="Resources-JCR-basedResources"></a></p>
+<p>The virtual Resource tree to which the the Resource accessor methods <code>resolve</code> and <code>getResource</code> provide access is implemented by a collection of registered <code>ResourceProvider</code> instances. The main Resource provider is of course the repository based <code>JcrResourceProvider</code> which supports Node and Property based resources. This Resource provider is always available in Sling. Further Resource providers may or may not exist.</p>
+<p>Each Resource provider is registered as an OSGi service with a required service registration property <code>provider.roots</code>. This is a multi-value String property listing the absolute paths Resource tree entries serving as roots to provided subtrees. For example, if a Resource provider is registered with the service registration property <code>provider.roots</code> set to <em>/some/root</em>, all paths starting with <code>/some/root</code> are first looked up in the given Resource Provider.</p>
+<p>When looking up a Resource in the registered Resource providers, the <code>ResourceResolver</code> applies a longest prefix matching algorithm to find the best match. For example consider three Resource provider registered as follows:
+<em> JCR Resource provider as <code>/</code>
+</em> Resource provider R1 as <code>/some</code>
+* Resource provider R2 as <code>/some/path</code></p>
+<p>When accessing a Resource with path <code>/some/path/resource</code> the Resource provider <em>R2</em> is first asked. If that cannot provide the resource, Resource provider <em>R1</em> is asked and finally the JCR Resource provider is asked. The first Resource provider having a Resource with the requested path will be used.</p>
 <h3 id="jcr-based-resources">JCR-based Resources</h3>
-<p>JCR-based Resources are provided with the default <em>JcrResourceProvider</em>.
-This Resource provider is always available and is always asked last. That
-is Resources provided by other Resource providers may never be overruled by
-repository based Resources.</p>
-<p><a name="Resources-Bundle-basedResources"></a></p>
+<p>JCR-based Resources are provided with the default <code>JcrResourceProvider</code>. This Resource provider is always available and is always asked last. That is Resources provided by other Resource providers may never be overruled by repository based Resources.</p>
 <h3 id="bundle-based-resources">Bundle-based Resources</h3>
-<p>Resources may by provided by OSGi bundles. Providing bundles have a Bundle
-manifest header <em>Sling-Bundle-Resources</em> containing a list of absolute
-paths provided by the bundle. The path are separated by comma or whitespace
-(SP, TAB, VTAB, CR, LF).</p>
-<p>The <em>BundleResourceProvider</em> supporting bundle-based Resources provides
-directories as Resources of type <em>nt:folder</em> and files as Resources of
-type <em>nt:file</em>. This matches the default primary node types intended to
-be used for directories and files in JCR repositories. For details see <a href="slingxsite:bundle-resources-(extensions.bundleresource).html">Bundle Resource.</a></p>
-<p><a name="Resources-ServletResources"></a></p>
+<p>Resources may by provided by OSGi bundles. Providing bundles have a Bundle manifest header <code>Sling-Bundle-Resources</code> containing a list of absolute paths provided by the bundle. The path are separated by comma or whitespace (SP, TAB, VTAB, CR, LF).</p>
+<p>The <code>BundleResourceProvider</code> supporting bundle-based Resources provides directories as Resources of type <code>nt:folder</code> and files as Resources of type <code>nt:file</code>. This matches the default primary node types intended to be used for directories and files in JCR repositories. For details see <a href="">Bundle Resource.</a></p>
 <h3 id="servlet-resources">Servlet Resources</h3>
-<p>Servlet Resources are registered by the Servlet Resolver bundle for
-Servlets registered as OSGi services. See <a href="slingxsite:servlets.html">Servlet Resolution</a>
- for information on how Servlet Resources are provided.</p>
-<p><a name="Resources-FileSystemResources"></a></p>
+<p>Servlet Resources are registered by the Servlet Resolver bundle for Servlets registered as OSGi services. See <a href="">Servlet Resolution</a> for information on how Servlet Resources are provided.</p>
 <h3 id="file-system-resources">File System Resources</h3>
-<p>The Filesystem Resource Provider provides access to the operating system's
-filesystem through the Sling ResourceResolver. Multiple locations may be
-mapped into the resource tree by configuring the filesystem location and
-the resource tree root path for each location to be mapped. For details see <a href="slingxsite:accessing-filesystem-resources-(extensions.fsresource).html">File System Resources</a>
-.</p>
-<p><a name="Resources-Wrap/DecorateResources"></a></p>
+<p>The Filesystem Resource Provider provides access to the operating system's filesystem through the Sling ResourceResolver. Multiple locations may be mapped into the resource tree by configuring the filesystem location and the resource tree root path for each location to be mapped. For details see <a href="">File System Resources</a>.</p>
 <h2 id="wrapdecorate-resources">Wrap/Decorate Resources</h2>
-<p>The Sling API provides an easy way to wrap or decorate a resource before
-returning. Details see <a href="wrap-or-decorate-resources.html">Wrap or Decorate Resources</a>
-.</p>
+<p>The Sling API provides an easy way to wrap or decorate a resource before returning. Details see <a href="/wrap-or-decorate-resources.html">Wrap or Decorate Resources</a>.</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

Added: websites/staging/sling/trunk/content/run-modes-org-apache-sling-runmode.html
==============================================================================
--- websites/staging/sling/trunk/content/run-modes-org-apache-sling-runmode.html (added)
+++ websites/staging/sling/trunk/content/run-modes-org-apache-sling-runmode.html Tue May 22 08:25:32 2012
@@ -0,0 +1,125 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<!--
+
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    contributor license agreements.  See the NOTICE file distributed with
+    this work for additional information regarding copyright ownership.
+    The ASF licenses this file to You under the Apache License, Version 2.0
+    (the "License"); you may not use this file except in compliance with
+    the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE- 2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
+  <head>
+    <title>Apache Sling - Run Modes (org.apache.sling.runmode)</title>
+    <link rel="stylesheet" href="/css/site.css" type="text/css" media="all">
+    <link rel="icon" href="http://sling.apache.org/site/media.data/favicon.ico">
+    <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
+  </head>
+  <body>
+    <div class="title">
+      <div class="logo">
+        <a href="http://sling.apache.org/site/index.html">
+          <img border="0" alt="Apache Sling" src="http://sling.apache.org/site/media.data/logo.png">
+        </a>
+      </div>
+      <div class="header">
+        <a href="http://www.apache.org/">
+          <img border="0" alt="Apache" src="http://sling.apache.org/site/media.data/apache.png">
+        </a>
+      </div>
+    </div>
+    
+    <div class="menu"> 
+      <p><strong>Documentation</strong> <br />
+<a href="/getting-started.html">Getting Started</a> <br />
+<a href="/the-sling-engine.html">The Sling Engine</a> <br />
+<a href="/development.html">Development</a> <br />
+<a href="/bundles.html">Bundles</a> <br />
+<a href="/tutorials-how-tos.html">Tutorials &amp; How-Tos</a> <br />
+<a href="/configuration.html">Configuration</a> <br />
+<a href="http://s.apache.org/sling.wiki">Wiki</a> <br />
+<a href="http://s.apache.org/sling.faq">FAQ</a> <br />
+<a href="/sitemap.html">Site Map</a></p>
+<p><strong>API Docs</strong>  <br />
+<a href="http://sling.apache.org/apidocs/sling6/index.html">Sling 6</a> <br />
+<a href="http://sling.apache.org/apidocs/sling5/index.html">Sling 5</a> <br />
+</p>
+<p><strong>Project info</strong> <br />
+<a href="http://sling.apache.org/site/downloads.cgi">Downloads</a> <br />
+<a href="http://www.apache.org/licenses/">License</a> <br />
+<a href="/contributing.html">Contributing</a> <br />
+<a href="/news.html">News</a> <br />
+<a href="/links.html">Links</a> <br />
+<a href="/project-information.html">Project Information</a> <br />
+<a href="https://issues.apache.org/jira/browse/SLING">Issue Tracker</a> <br />
+<a href="http://svn.apache.org/viewvc/sling/trunk">Browse Source Repository</a> <br />
+<a href="/security.html">Security</a> <br />
+</p>
+<p><strong>Sponsorship</strong> <br />
+<a href="http://www.apache.org/foundation/thanks.html">Thanks</a> <br />
+<a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a> <br />
+<a href="http://www.apache.org/foundation/buy_stuff.html">Buy Stuff</a> <br />
+</p>
+<iframe 
+    src="http://www.apache.org/ads/button.html"
+    style="border-width:0; float: left" frameborder="0" 
+    scrolling="no"
+    width="135" 
+    height="135">
+</iframe>
+    </div>
+    
+    <div class="main">
+      <div class="breadcrump" style="font-size: 80%;">
+        <a href="/">Home</a>
+      </div>
+      <h1>Run Modes (org.apache.sling.runmode)</h1>
+      <p>{note}
+As of Sling 6 the <code>org.apache.sling.runmode</code> bundle is replaced by the new <a href="/sling-settings-org-apache-sling-settings.html">Sling Settings (org.apache.sling.settings)</a> Bundle. For backwards compatibility this bundle may still exist in your environment. New code should use the API of the new [Sling Settings (org.apache.sling.settings)] Bundle, though.
+{note}</p>
+<h1 id="overview">Overview</h1>
+<p>Run modes are meant to define different sets of configuration parameters for various Sling instances.</p>
+<p>In a web publishing environment, for example, one could use run modes like <em>staging, production, dev, dmz</em> or combinations of such values.</p>
+<p>The <em><a href="">org.apache.sling.runmode</a></em> bundle provides a simple way of defining and querying a list of run modes.</p>
+<h1 id="installation">Installation</h1>
+<p>The run mode service is not present in the default Sling launchpad builds, to activate it install and start the <em>org.apache.sling.runmode</em> bundle.</p>
+<h1 id="configuration">Configuration</h1>
+<p>Run modes can only be configured using a system property, or via the <em>sling.properties</em> file.</p>
+<p>Using <em>-Dsling.run.modes=foo,bar</em> on the JVM command-line, for example, activates the <em>foo</em> and <em>bar</em> run modes. </p>
+<p>This command-line parameter takes precedence over a similar definition (<em>sling.run.modes=dev,staging</em>) that might be present in the <em>sling.properties</em> file found in the Sling home directory.</p>
+<h1 id="getting-the-current-list-of-run-modes">Getting the current list of run modes</h1>
+<p>The <a href="">RunMode service</a> provides the current list of run modes, examples:</p>
+<p><DIV class="code panel" style="border-style: solid;border-width: 1px;"><DIV class="codeHeader panelHeader" style="border-bottom-width: 1px;border-bottom-style: solid;"><B>RunMode examples</B></DIV><DIV class="codeContent panelContent">
+    RunMode r = ...get from BundleContext...
+    String [] currentRunModes = r.getCurrentRunModes();</p>
+<div class="codehilite"><pre><span class="n">String</span> <span class="o">[]</span> <span class="n">expectedRunModes</span> <span class="o">=</span> <span class="p">{</span> <span class="s">&quot;foo&quot;</span><span class="p">,</span> <span class="s">&quot;wii&quot;</span> <span class="p">};</span>
+<span class="k">if</span><span class="p">(</span><span class="n">r</span><span class="o">.</span><span class="n">isActive</span><span class="p">(</span><span class="n">expectedRunModes</span><span class="p">))</span> <span class="p">{</span>
+  <span class="sr">//</span> <span class="n">at</span> <span class="n">least</span> <span class="n">one</span> <span class="n">of</span> <span class="p">(</span><span class="n">foo</span><span class="p">,</span><span class="n">wii</span><span class="p">)</span> <span class="n">run</span> <span class="n">modes</span>
+  <span class="sr">//</span> <span class="n">is</span> <span class="n">active</span>
+<span class="p">}</span>
+</pre></div>
+
+
+<h1 id="see-also">See also</h1>
+<p>The RunMode service is used by the <a href="/jcr-installer-provider.html">jcrinstall</a> services.</p>
+<h1 id="automated-tests">Automated tests</h1>
+<p>The <a href="">RunModeImplTest class</a> provides more info about run modes parsing and usage.</p>
+      <div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
+        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
+        logo are trademarks of The Apache Software Foundation. All other marks mentioned
+        may be trademarks or registered trademarks of their respective owners.
+      </div>
+    </div>
+  </body>
+</html>



Mime
View raw message