[
https://issues.apache.org/jira/browse/SLING-6578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-6578:
-----------------------------------
Description: 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". (was: 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.)
> 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)
