[jira] [Assigned] (SLING-4157) Allow Sling validation to pick up models in any location in the repository

["Konrad Windszus (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konrad Windszus reassigned SLING-4157:
--------------------------------------

    Assignee: Konrad Windszus

> Allow Sling validation to pick up models in any location in the repository
> --------------------------------------------------------------------------
>
>                 Key: SLING-4157
>                 URL: https://issues.apache.org/jira/browse/SLING-4157
>             Project: Sling
>          Issue Type: Improvement
>          Components: Validation
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>              Labels: patch
>
> Currently only validation models being defined below
> * /apps/sling/validation/models/ and
> * /libs/sling/validation/models/ 
> are picked up
> This is due to the XPath query containing the path restriction (in https://github.com/apache/sling/blob/trunk/contrib/validation/core/src/main/java/org/apache/sling/validation/impl/ValidationServiceImpl.java#L295).
> Similar to the JCR Repository based ResourceBundleProvider ( http://sling.apache.org/site/internationalization-support.html) the validation models should be allowed  everywhere in the repository (where apps should still have higher priority than libs). That should not have a major performance drawback.
> This is especially useful, if multiple different applications are deployed on the same Sling instance. To be able to distinguish their scripts and validation models in the repository (and to not overwrite other applications' models) it should be allowed that everything belonging to that one application is located below one common entry node (e.g. /apps/mycoolslingapp/)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)