You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Henning Schmiedehausen (JIRA)" <de...@velocity.apache.org> on 2007/03/08 01:04:39 UTC
[jira] Closed: (VELOCITY-284) MethodInvocationException is handled
inconsistently
[ https://issues.apache.org/jira/browse/VELOCITY-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Henning Schmiedehausen closed VELOCITY-284.
-------------------------------------------
> MethodInvocationException is handled inconsistently
> ---------------------------------------------------
>
> Key: VELOCITY-284
> URL: https://issues.apache.org/jira/browse/VELOCITY-284
> Project: Velocity
> Issue Type: Improvement
> Components: Engine
> Affects Versions: 1.4, 1.5
> Environment: Operating System: All
> Platform: Other
> Reporter: Mike Rettig
> Assigned To: Will Glass-Husain
> Priority: Minor
> Fix For: 1.5
>
> Attachments: swallowed_exception.txt
>
>
> It appears that the exception handling is different depending on whether the
> method is invoked as a passed parameter to a velocimacro or just in a template.
> Ex.
> #doTextLink( ${myObj.exception})
> ${myObj.exception}
> The first #doTextLink macro will throw an exception, but it will be logged and
> ignored. However, the second invocation will throw the exception properly.
> I have a patch that should fix this behavior. The exception just needs to be
> rethrown up the call stack. A small signature change to a couple of methods.
> Thanks,
> Mike Rettig
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org