Uploaded image for project: 'Velocity'
  1. Velocity
  2. VELOCITY-284

MethodInvocationException is handled inconsistently

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • 1.4, 1.5
    • 1.5
    • Engine
    • None
    • Operating System: All
      Platform: Other
    • 30220

    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

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            wglass William Glass-Husain
            mike.rettig@gmail.com Mike Rettig
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment