Tapestry 5
  1. Tapestry 5
  2. TAP5-1732

Tapestry should not swallow client-side initialization exceptions, as that makes it harder to debug

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 5.3
    • Fix Version/s: 5.3
    • Component/s: tapestry-core
    • Labels:

      Description

      Unlike Java, JavaScript has not concept of a nested exception, so that means intercepting an initialization exception so report it ultimately makes it harder to debug: even using a client debugger, there's no way to see the origin of the exception (the way you would find a nested exception in Java), and the error console output reporting the exception reports the stack trace only up to the code that caught the exception and invoked t5.console.error(), rather than the underlying exception.

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Howard M. Lewis Ship
            Reporter:
            Howard M. Lewis Ship
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development