[
https://issues.apache.org/jira/browse/SLING-5829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15367653#comment-15367653
]
Steven Walters commented on SLING-5829:
---------------------------------------
Fair enough I suppose, though I'm not currently seeing such a ticket or
discussion related to transitioning from SERVICE_PID to
ResourceProvider.PROPERTY_NAME as mentioned here. (e.g. don't want this
necessity to be lost)
Such a change would also break existing configurations that utilize the
matching behavior on SERVICE_PID, possibly requiring configuration updates to
be made on upgrade, so will likely need mentioning in any such release notes
for higher tier applications, such as AEM.
> Fix handling of SERVICE_PID
> ---------------------------
>
> Key: SLING-5829
> URL: https://issues.apache.org/jira/browse/SLING-5829
> Project: Sling
> Issue Type: Bug
> Components: ResourceResolver
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Resource Resolver 1.5.0
>
>
> The value of the service property SERVICE_PID can either be String or
> String[]. We should guard against String[].
> The resource resolver uses the PID for configuring required resource providers
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
