Tapestry should not swallow client-side initialization exceptions, as that
makes it harder to debug
---------------------------------------------------------------------------------------------------
Key: TAP5-1732
URL: https://issues.apache.org/jira/browse/TAP5-1732
Project: Tapestry 5
Issue Type: Bug
Components: tapestry-core
Affects Versions: 5.3
Reporter: Howard M. Lewis Ship
Priority: Critical
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
