Mailing-List: contact commits-help@tapestry.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@tapestry.apache.org
Date: Thu, 27 Oct 2011 19:04:32 +0000 (UTC)
From: "Howard M. Lewis Ship (Closed) (JIRA)" <jira@apache.org>
To: commits@tapestry.apache.org
Message-ID: 
 <1990418749.25988.1319742272362.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <999075165.25946.1319741672675.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Closed] (TAP5-1732) Tapestry should not swallow client-side
 initialization exceptions, as that makes it harder to debug
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/TAP5-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship closed TAP5-1732.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: 5.3
         Assignee: Howard M. Lewis Ship
    
> 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
>            Assignee: Howard M. Lewis Ship
>            Priority: Critical
>              Labels: javascript
>             Fix For: 5.3
>
>
> 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