[SLING-6534] Optionally cache results of ValidationService.validate(Resource, ValidationModel) and expose the cached result via an AdapterFactory

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Validation 1.0.0
• Component/s: Validation
• Assignee: Konrad Windszus
• Reporter: Konrad Windszus
• Created: 20/Feb/17 16:05
• Updated: 20/Sep/17 13:17
• Resolved: 21/Feb/17 10:40

Description

At least for the Sling Validation being triggered from the ModelAdapterFactory it would be beneficial to be able to look up the result of the last validation of a specific resource in a cache. That is especially useful when exceptions cannot be used to propagate this information to a different place in the code (e.g. to a Servlet filter). A concrete use case for this is SLING-6531 where the cached result is accessible even if all failures are below the threshold.

Issue Links

• relates to: SLING-6531 Do not always throw exceptions to propagate information about failed validations