You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2017/03/07 15:43:38 UTC
[jira] [Resolved] (SLING-6613) ResourceResolverFactory not
registered when legacy configuration references JcrResourceProviderFactory
[ https://issues.apache.org/jira/browse/SLING-6613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Munteanu resolved SLING-6613.
------------------------------------
Resolution: Fixed
Fixed in [r1785849|https://svn.apache.org/r1785849]
> ResourceResolverFactory not registered when legacy configuration references JcrResourceProviderFactory
> ------------------------------------------------------------------------------------------------------
>
> Key: SLING-6613
> URL: https://issues.apache.org/jira/browse/SLING-6613
> Project: Sling
> Issue Type: Bug
> Components: ResourceResolver
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Fix For: Resource Resolver 1.5.20
>
> Attachments: 0001-SLING-6613-ResourceResolverFactory-not-registered-wh.patch
>
>
> The fix for SLING-6469 references a legacy service pid of {{org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProvider}}. However, in my tests the actual pid is {{org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProviderFactory}} ( note the factory at the end ).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)