You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2015/12/30 10:31:49 UTC

[jira] [Closed] (SLING-5019) ServiceUserMappedBundleFilter should be immediate

     [ https://issues.apache.org/jira/browse/SLING-5019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler closed SLING-5019.
-----------------------------------

> ServiceUserMappedBundleFilter should be immediate
> -------------------------------------------------
>
>                 Key: SLING-5019
>                 URL: https://issues.apache.org/jira/browse/SLING-5019
>             Project: Sling
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: Service User Mapper 1.2.0
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: Service User Mapper 1.2.2
>
>
> The ServiceUserMappedBundleFilter implements two service hooks. The framework implementation gets/ungets the hooks on demand which results in this component getting activated/deactivated over and over again.
> While the framework impl is not optimal, we should declare this component immediate to avoid such a scenario regardless of the framework impl



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)