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 2013/04/04 11:40:26 UTC
svn commit: r857224 - in /websites/staging/sling/trunk/content: ./
documentation/the-sling-engine/filters.html
Author: buildbot
Date: Thu Apr 4 09:40:26 2013
New Revision: 857224
Log:
Staging update by buildbot for sling
Modified:
websites/staging/sling/trunk/content/ (props changed)
websites/staging/sling/trunk/content/documentation/the-sling-engine/filters.html
Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Apr 4 09:40:26 2013
@@ -1 +1 @@
-1464392
+1464399
Modified: websites/staging/sling/trunk/content/documentation/the-sling-engine/filters.html
==============================================================================
--- websites/staging/sling/trunk/content/documentation/the-sling-engine/filters.html (original)
+++ websites/staging/sling/trunk/content/documentation/the-sling-engine/filters.html Thu Apr 4 09:40:26 2013
@@ -160,22 +160,27 @@
<p>Note on <code>INCLUDE</code> and <code>FORWARD</code> with respect to JSP tags: These filters are also called if the respective including (e.g. <code><jsp:include></code> or <code><sling:include></code>) or forwarding (e.g. <code><jsp:forward></code> or <code><sling:forward></code>) ultimately calls the <code>RequestDispatcher</code>.</p>
<h2 id="filter-processing">Filter Processing</h2>
<p>Filter processing is part of the Sling request processing, which may be sketched as follows:</p>
-<p>| <em>Request Level</em> |
-| Authentication |
-| Resource Resolution |
-| Servlet/Script Resolution |
-| Request Level Filter Processing |
-| <em>Component Level</em> |</p>
+<ul>
+<li><em>Request Level</em>:</li>
+<li>Authentication</li>
+<li>Resource Resolution</li>
+<li>Servlet/Script Resolution</li>
+<li>Request Level Filter Processing</li>
+</ul>
<p>The first step of request processing is the <em>Request Level</em> processing which is concerned with resolving the resource, finding the appropriate servlet and calling into the request level filter chain. The next step is the <em>Component Level</em> processing, calling into the component level filters before finally calling the servlet or script:</p>
-<p>| <em>Component Level</em> |
-| Component Level Filter Processing |
-| Call Servlet or Script |</p>
+<ul>
+<li><em>Component Level</em>:</li>
+<li>Component Level Filter Processing</li>
+<li>Call Servlet or Script</li>
+</ul>
<p>When a servlet or script is including or forwarding to another resource for processing through the <code>RequestDispatcher</code> (or any JSP tag or other language feature ultimately using a <code>RequestDispatcher</code>) the following <em>Dispatch</em> processing takes place:</p>
-<p>| <em>Dispatch</em> |
-| Resolve the resource to dispatch to if not already defined when getting the <code>RequestDispatcher</code> |
-| Servlet/Script resolution |
-| Call include or forward filters depending on the kind of dispatch |
-| Call Servlet or Script |</p>
+<ul>
+<li><em>Dispatch</em>:</li>
+<li>Resolve the resource to dispatch to if not already defined when getting the <code>RequestDispatcher</code></li>
+<li>Servlet/Script resolution</li>
+<li>Call include or forward filters depending on the kind of dispatch</li>
+<li>Call Servlet or Script</li>
+</ul>
<p>As a consequence, request level filters will be called at most once during request processing (they may not be called at all if a filter earlier in the filter chain decides to terminate the request) while the component level, include, and forward filters may be called multiple times while processing a request.</p>
<h2 id="troubleshooting">Troubleshooting</h2>
<p>Apart form the logs which tell you when filters are executed, two Sling plugins provide information about filters in the OSGi console.</p>
@@ -231,7 +236,7 @@
<li>Filter ordering is defined by the <code>filter.order</code> property whose default value is <code>Integer.MAX_VALUE</code> where smaller values have higher priority over higher values.</li>
</ul>
<div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
- Rev. 1464392 by bdelacretaz on Thu, 4 Apr 2013 09:31:47 +0000
+ Rev. 1464399 by bdelacretaz on Thu, 4 Apr 2013 09:40:20 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project