You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2011/09/23 19:49:26 UTC

[jira] [Closed] (TAP5-1369) ExceptionUtils.findCause() does not use the same approach as ExceptionAnalyzer

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

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

       Resolution: Fixed
    Fix Version/s: 5.3

> ExceptionUtils.findCause() does not use the same approach as ExceptionAnalyzer
> ------------------------------------------------------------------------------
>
>                 Key: TAP5-1369
>                 URL: https://issues.apache.org/jira/browse/TAP5-1369
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-ioc
>    Affects Versions: 5.2.4
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>            Priority: Minor
>             Fix For: 5.3
>
>
> findCause() only works using the cause property, whereas in many cases (older code typically that predates the cause property, introduced in JDK 1.4)) there's an alternate property that stores the actual nested exception.
> ExceptionAnalyzer does it correctly, at higher cost (lots of property access to identify the cause).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira