[SLING-4161] Support Sling Validation through a new field of the Model annotation

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Sling Models API 1.0.0, Sling Models Implementation 1.0.0
• Fix Version/s: Sling Models API 1.2.0, Sling Models Impl 1.2.0, Models Validation Impl 1.0.0
• Component/s: Extensions
• Assignee: Konrad Windszus
• Reporter: Konrad Windszus
• Created: 13/Nov/14 16:57
• Updated: 18/Dec/15 09:49
• Resolved: 03/Jun/15 07:40

Description

The current way of integrating Sling Validation (SLING-2803) with Sling Models is to inject the validation service and then call it within a PostConstruct method (http://www.slideshare.net/raducotescu/apache-sling-generic-validation-framework/16).
This has the drawback that

1. the ValidationService needs to be injected
2. a PostConstruct needs to be implemented
3. the other injections need to be marked as optional (otherwise the validation is never triggered in case of e.g. missing required valuemap values)

Instead it would be good to support this use case with just an additional field on the annotation Model which is named validate. By default this should be false (to be backwards compatible), but if it is true the Sling Validation should be called before any values are injected into the model. If validation fails the ModelAdapterFactory should never instanciate the model and rather return null (or throw a meaningful exception for SLING-3709).

Issue Links

• is blocked by: SLING-4606 Move validation from contrib to /
• is related to: SLING-5389 Sling Models: Do not swallow PostConstruct exceptions