[
https://issues.apache.org/jira/browse/SLING-6613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15899613#comment-15899613
]
Robert Munteanu commented on SLING-6613:
----------------------------------------
I've double-checked a Sling 8 instance and indeed the actual service PID for
the required provider is
{{org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProviderFactory}}.
I will commit the change as-is.
> 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)
