incubator-sling-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bdelacre...@apache.org
Subject svn commit: r1464399 - /sling/site/trunk/content/documentation/the-sling-engine/filters.mdtext
Date Thu, 04 Apr 2013 09:40:20 GMT
Author: bdelacretaz
Date: Thu Apr  4 09:40:20 2013
New Revision: 1464399

URL: http://svn.apache.org/r1464399
Log:
fix filter processing steps formatting

Modified:
    sling/site/trunk/content/documentation/the-sling-engine/filters.mdtext

Modified: sling/site/trunk/content/documentation/the-sling-engine/filters.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/the-sling-engine/filters.mdtext?rev=1464399&r1=1464398&r2=1464399&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/the-sling-engine/filters.mdtext (original)
+++ sling/site/trunk/content/documentation/the-sling-engine/filters.mdtext Thu Apr  4 09:40:20
2013
@@ -37,30 +37,28 @@ Note on `INCLUDE` and `FORWARD` with res
 
 Filter processing is part of the Sling request processing, which may be sketched as follows:
 
-| *Request Level* |
-| Authentication |
-| Resource Resolution |
-| Servlet/Script Resolution |
-| Request Level Filter Processing |
-| *Component Level* |
+* *Request Level*:
+ * Authentication
+ * Resource Resolution
+ * Servlet/Script Resolution
+ * Request Level Filter Processing
 
 The first step of request processing is the *Request Level* 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 *Component Level* processing, calling into the component
level filters before finally calling the servlet or script:
 
-| *Component Level* |
-| Component Level Filter Processing |
-| Call Servlet or Script |
+* *Component Level*:
+ * Component Level Filter Processing
+ * Call Servlet or Script
 
 When a servlet or script is including or forwarding to another resource for processing through
the `RequestDispatcher` (or any JSP tag or other language feature ultimately using a `RequestDispatcher`)
the following *Dispatch* processing takes place:
 
-| *Dispatch* |
-| Resolve the resource to dispatch to if not already defined when getting the `RequestDispatcher`
|
-| Servlet/Script resolution |
-| Call include or forward filters depending on the kind of dispatch |
-| Call Servlet or Script |
+* *Dispatch*:
+ * Resolve the resource to dispatch to if not already defined when getting the `RequestDispatcher`
+ * Servlet/Script resolution
+ * Call include or forward filters depending on the kind of dispatch
+ * Call Servlet or Script
 
 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.
 
-
 ## Troubleshooting
 Apart form the logs which tell you when filters are executed, two Sling plugins provide information
about filters in the OSGi console.
 



Mime
View raw message