You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Christopher Schultz (JIRA)" <ji...@apache.org> on 2016/08/11 02:38:20 UTC

[jira] [Commented] (VELOCITY-798) Velocity wraps java.lang.Error in org.apache.velocity.exception.MethodInvocationException

    [ https://issues.apache.org/jira/browse/VELOCITY-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15416412#comment-15416412 ] 

Christopher Schultz commented on VELOCITY-798:
----------------------------------------------

I would argue that java.lang.Error should not be caught and re-thrown as another exception. If you want to use a catch block for something, the original Error should be re-thrown at the end of it.

> Velocity wraps java.lang.Error in org.apache.velocity.exception.MethodInvocationException
> -----------------------------------------------------------------------------------------
>
>                 Key: VELOCITY-798
>                 URL: https://issues.apache.org/jira/browse/VELOCITY-798
>             Project: Velocity
>          Issue Type: Bug
>          Components: Engine
>    Affects Versions: 1.7
>         Environment: n.a.
>            Reporter: Alexander Veit
>
> If a method call throws a java.lang.Error, Velocity wraps it in a MethodInvocationException, which itself is not a java.lang.Error.
> The spec says: "An Error is a subclass of Throwable that indicates serious problems that a reasonable application should not try to catch."
> Wrapping the error hides it from applications and makes it difficult to handle.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org