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 2017/01/16 15:35:26 UTC

[jira] [Updated] (SLING-6469) Resource Resolver Factory does not start if updating from an older version

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

Carsten Ziegeler updated SLING-6469:
------------------------------------
    Component/s: ResourceResolver

> Resource Resolver Factory does not start if updating from an older version
> --------------------------------------------------------------------------
>
>                 Key: SLING-6469
>                 URL: https://issues.apache.org/jira/browse/SLING-6469
>             Project: Sling
>          Issue Type: Bug
>          Components: ResourceResolver
>    Affects Versions: Resource Resolver 1.5.10
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: Resource Resolver 1.5.12
>
>
> If the resource resolver bundle is updated and it exists a configuration for the "old" resource resolver factory, then this one contains usually a precondition on having the JCR resource provider. With the move to the new SPI this JCR resource provider does not use the PID anymore and therefore the precondition check fails



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