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/02/20 14:18:44 UTC
[jira] [Updated] (SLING-6531) Do not always throw exceptions to
propagate information about failed validations
[ https://issues.apache.org/jira/browse/SLING-6531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus updated SLING-6531:
-----------------------------------
Description: Right now the {{o.a.s.models.validation.impl.ModelValidationImpl}} will always throw an {{InvalidResourceException}} in case the underlying resource is not valid (according to Sling Validation). With the advent of different severities per issue (SLING-5373) this seems a bit too strict because some validators could be used just for informational purposes. Those validations should not prevent the Sling Model from being instantiated.
> Do not always throw exceptions to propagate information about failed validations
> --------------------------------------------------------------------------------
>
> Key: SLING-6531
> URL: https://issues.apache.org/jira/browse/SLING-6531
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: Sling Models Validation Impl 1.0.0
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Fix For: Sling Models Validation Impl 1.0.0
>
>
> Right now the {{o.a.s.models.validation.impl.ModelValidationImpl}} will always throw an {{InvalidResourceException}} in case the underlying resource is not valid (according to Sling Validation). With the advent of different severities per issue (SLING-5373) this seems a bit too strict because some validators could be used just for informational purposes. Those validations should not prevent the Sling Model from being instantiated.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)