[DISCUSS] Registering filters with Sling

Hi all, Traditionally javax.servlet.Filter services were picked up by the Sling Main Servlet and used as filters regardless of any service registration properties. The filter.scope property could optionally be used to define a scope for the filter (request or component before SLING-1213, now also

Re: [DISCUSS] Registering filters with Sling

+1 On 9/7/10 9:49 AM, Felix Meschberger wrote: Hi all, Traditionally javax.servlet.Filter services were picked up by the Sling Main Servlet and used as filters regardless of any service registration properties. The filter.scope property could optionally be used to define a scope for the

Re: [DISCUSS] Registering filters with Sling

Ian Boston wrote On 7 Sep 2010, at 14:49, Felix Meschberger wrote: Hi all, Traditionally javax.servlet.Filter services were picked up by the Sling Main Servlet and used as filters regardless of any service registration properties. The filter.scope property could optionally be used to

Re: [DISCUSS] Registering filters with Sling

Felix Meschberger wrote The order property has already been deprecated in favor of the OSGi standard service.ranking property (as of FELIX-1213). Perfect :) Carsten -- Carsten Ziegeler cziege...@apache.org

Re: [DISCUSS] Registering filters with Sling

Hi all, Thanks for the feedback so far. I have created SLING-1734 [1] to track this change. Regards Felix [1] https://issues.apache.org/jira/browse/SLING-1734 On 07.09.2010 15:49, Felix Meschberger wrote: Hi all, Traditionally javax.servlet.Filter services were picked up by the Sling Main