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

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 5.3
• Fix Version/s: 5.3
• Component/s: tapestry-core
• Labels: javascript
• Assignee: Howard Lewis Ship
• Reporter: Howard Lewis Ship
• Created: 27/Oct/11 18:54
• Updated: 27/Oct/11 20:56
• Resolved: 27/Oct/11 19:03

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.