[
https://issues.apache.org/jira/browse/SLING-3346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved SLING-3346.
--------------------------------------
Resolution: Fixed
Fix Version/s: Resource Resolver 1.1.0
Turns out we need both filter registration because initial resource resolution
takes place before any Sling filter is called
An additional issues was unconvered where negative feature checks had no effect
Fixed both issues in Rev. 1562416
> Feature#isEnabled(ExecutionContext) method not evaluated
> --------------------------------------------------------
>
> Key: SLING-3346
> URL: https://issues.apache.org/jira/browse/SLING-3346
> Project: Sling
> Issue Type: Bug
> Components: Extensions, ResourceResolver
> Reporter: Simone Tripodi
> Assignee: Felix Meschberger
> Fix For: Resource Resolver 1.1.0
>
>
> It is enough for a _Resource_ having the {{sling:features}} property set with
> a valid _Feature_ service name to be disabled -and dropping it re-enables the
> _Resource_- it doesn't matter which boolean value the method
> {{Feature#isEnabled(ExecutionContext)}} returns, it is not hit neither
> evaluated.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
