Author: bdelacretaz
Date: Mon May 18 08:21:14 2015
New Revision: 1679956
URL: http://svn.apache.org/r1679956
Log:
SLING-4294 - clarify docs
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=1679956&r1=1679955&r2=1679956&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/the-sling-engine/filters.mdtext
(original)
+++ sling/site/trunk/content/documentation/the-sling-engine/filters.mdtext Mon
May 18 08:21:14 2015
@@ -16,7 +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 |
+| `sling.filter.pattern` | `String`| `` | Any `String` value | Restrict the
filter to paths that match the supplied regular expression. Requires Sling
Engine 2.4.0. |
| `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. |
