You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Will Glass-Husain (JIRA)" <ji...@apache.org> on 2006/11/10 16:22:44 UTC
[jira] Resolved: (VELOCITY-284) MethodInvocationException is
handled inconsistently
[ http://issues.apache.org/jira/browse/VELOCITY-284?page=all ]
Will Glass-Husain resolved VELOCITY-284.
----------------------------------------
Fix Version/s: 1.5
(was: 2.0)
(was: 1.6)
Resolution: Fixed
rsolved again. r473363
> MethodInvocationException is handled inconsistently
> ---------------------------------------------------
>
> Key: VELOCITY-284
> URL: http://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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org