[jira] Updated: (VELOCITY-284) MethodInvocationException is handled inconsistently

["Will Glass-Husain (JIRA)" <ji...@apache.org>]

     [ http://issues.apache.org/jira/browse/VELOCITY-284?page=all ]

Will Glass-Husain updated VELOCITY-284:
---------------------------------------

    Bugzilla Id:   (was: 30220)
           type: Improvement  (was: Bug)
    Fix Version: 2.0
    Description: 
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

  was:
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

    Environment: 
Operating System: All
Platform: Other

  was:
Operating System: All
Platform: Other

      Assign To:     (was: Velocity-Dev List)
       Priority: Minor  (was: Major)

> MethodInvocationException is handled inconsistently
> ---------------------------------------------------
>
>          Key: VELOCITY-284
>          URL: http://issues.apache.org/jira/browse/VELOCITY-284
>      Project: Velocity
>         Type: Improvement
>   Components: Source
>     Versions: 1.4
>  Environment: Operating System: All
> Platform: Other
>     Reporter: Mike Rettig
>     Priority: Minor
>      Fix For: 2.0
>  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