You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Konrad Windszus (JIRA)" <ji...@apache.org> on 2017/03/02 07:48:45 UTC

[jira] [Updated] (SLING-6578) Use "validator.id" property instead of class name to reference validators

     [ 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 "validator.id" 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. Using a predefined property like "service.pid" or "component.name" is not possible/recommended, as those are used for other purposes and are not necessarily there under all circumstances.  (was: Leveraging the component's "validation.id" 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. Using a predefined property like "service.pid" or "component.name" is not possible/recommended, as those are used for other purposes and are not necessarily there under all circumstances.)

> Use "validator.id" 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
>          Components: Validation
>    Affects Versions: Validation 1.0.0
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>             Fix For: Validation 1.0.0
>
>         Attachments: SLING-6578-v01.patch
>
>
> Leveraging the component's "validator.id" 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. Using a predefined property like "service.pid" or "component.name" is not possible/recommended, as those are used for other purposes and are not necessarily there under all circumstances.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)