[
https://issues.apache.org/jira/browse/SLING-4012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14209462#comment-14209462
]
ASF GitHub Bot commented on SLING-4012:
---------------------------------------
Github user kwin closed the pull request at:
https://github.com/apache/sling/pull/29
> 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
> Fix For: Validation 1.0.0
>
>
> 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)
