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

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Validation 1.0.0
• Component/s: Validation
• Labels: patch
• Assignee: Konrad Windszus
• Reporter: Konrad Windszus
• Created: 12/Nov/14 10:38
• Updated: 20/Sep/17 13:17
• Resolved: 12/Nov/14 17:34

Description

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/)

Issue Links

• is related to: SLING-5660 Validation is using outdated sling/validation/model