You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by bu...@apache.org on 2004/07/20 21:37:49 UTC
DO NOT REPLY [Bug 30219] New: -
MethodInvocationException is handled inconsistently
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=30219>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=30219
MethodInvocationException is handled inconsistently
Summary: MethodInvocationException is handled inconsistently
Product: Velocity
Version: 1.4
Platform: Other
OS/Version: All
Status: NEW
Severity: Normal
Priority: Other
Component: Source
AssignedTo: velocity-dev@jakarta.apache.org
ReportedBy: mike.rettig@gmail.com
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
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org