[
https://issues.apache.org/jira/browse/SLING-6578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890027#comment-15890027
]
Felix Meschberger commented on SLING-6578:
------------------------------------------
I don't understand this ?
Is the general use of the service.pid property tied to Configuration Admin ? It
is not. To the contrary. Configuration Admin is just reusing it for its own
purposes with two specific services: ManagedService and ManagedServiceFactory.
Configuration Admin does not generalize the use of service.pid.
Declarative Services goes another step by using the component name (or
configuration-pid) as the identifier for the configuration which causes the
service.pid to be set as if Configuration Admin would provide configuration to
ManagedService or ManagedServiceFactory.
This might lead to that misconception. But this is not forced. By simply
setting a service.pid component property you get the desired result.
> Use "service.pid" property instead of class name to reference validators
> ------------------------------------------------------------------------
>
> Key: SLING-6578
> URL: https://issues.apache.org/jira/browse/SLING-6578
> Project: Sling
> Issue Type: Improvement
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
>
> Leveraging the component's "service.pid" property value instead of its
> classname is more stable (even if implementation changes, the PID might stay
> the same) and also allows for configuration factories to refer to a specific
> validator configuration. The fallback should be the property "component.name"
> as "service.pid" is not always necessarily set. Basically the validator
> should be referable via each of those value, i.e. one of the "service.pid"s
> or the "component.name".
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
