svn commit: r1656709 - /sling/site/trunk/content/documentation/the-sling-engine/filters.mdtext

[as...@apache.org]

Author: asanso
Date: Tue Feb  3 12:41:51 2015
New Revision: 1656709

URL: http://svn.apache.org/r1656709
Log:
SLING-4294 - Servlet Filter Support adding sling.filter.pattern support

* adding site documentation

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=1656709&r1=1656708&r2=1656709&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/the-sling-engine/filters.mdtext (original)
+++ sling/site/trunk/content/documentation/the-sling-engine/filters.mdtext Tue Feb  3 12:41:51 2015
@@ -16,6 +16,7 @@ For Sling to pick up a `javax.servlet.Fi
 | Property | Type | Default Value | Valid Values | Description |
 |--|--|--|--|--|
 | `sling.filter.scope` | `String`, `String[]({{ refs..path }})` or `Vector<String>` | `request` | `REQUEST`, `INCLUDE`, `FORWARD`, `ERROR`, `COMPONENT` | Indication of which chain the filter should be added to. This property is required. If it is missing from the service, the service is ignored because it is assumed another consumer will be interested in using the service. Any unknown values of this property are also ignored causing the service to be completely ignored if none of the values provided by the property are valid. See below for the description of the filter chains. |
+| `sling.filter.pattern` | `String`| `` | Any `String` value | The regular expression pattern to register filter with |
 | `service.ranking` | `Integer` | `0` | Any `Integer` value | Indication of where to place the filter in the filter chain. The higher the number the earlier in the filter chain. This value may span the whole range of integer values. Two filters with equal `service.ranking` property value (explicitly set or default value of zero) will be ordered according to their `service.id` service property as described in section 5.2.5, Service Properties, of the OSGi Core Specification R 4.2. |