You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2014/10/08 11:20:34 UTC

[jira] [Updated] (SLING-4012) Do not catch SlingValidationExceptions in the ValidationServiceImpl.java

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

Bertrand Delacretaz updated SLING-4012:
---------------------------------------
    Component/s:     (was: Extensions)
                 Validation

> Do not catch SlingValidationExceptions in the ValidationServiceImpl.java
> ------------------------------------------------------------------------
>
>                 Key: SLING-4012
>                 URL: https://issues.apache.org/jira/browse/SLING-4012
>             Project: Sling
>          Issue Type: Improvement
>          Components: Validation
>            Reporter: Konrad Windszus
>            Assignee: Bertrand Delacretaz
>              Labels: validator
>
> Currently all SlingValidationExceptions are caught in the ValidationServiceImpl.java (https://github.com/apache/sling/blob/trunk/contrib/validation/core/src/main/java/org/apache/sling/validation/impl/ValidationServiceImpl.java#L384). Since those exceptions should only happen during development, it would be very good, if those exceptions would not be caught by the ValidationServiceImpl. That way the exception is printed in most of the cases directly into the response (i.e. is easier to see during development time). Also features like a custom exception handler (through a servlet filter) or the AEM error filter could be used to expose that exception.



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