[
https://issues.apache.org/jira/browse/SLING-6578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890005#comment-15890005
]
Carsten Ziegeler commented on SLING-6578:
-----------------------------------------
service.pid is not reliable - with a DS component you only have a service.pid
if the component is configurable through an OSGi configuration *and* such a
configuration exists.
For exactly this reason we have to change some of our implementations as they
were using service.pid as a reference which turned out to be a bad idea.
In addition dealing with service pid is a little bit of a pain as it can be a
string or a string array.
A separate property is imho the better choice
> 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)
