You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2011/09/23 20:34:26 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13113642#comment-13113642 ]
Hudson commented on TAP5-1369:
------------------------------
Integrated in tapestry-trunk-freestyle #537 (See [https://builds.apache.org/job/tapestry-trunk-freestyle/537/])
TAP5-1369: ExceptionUtils.findCause() does not use the same approach as ExceptionAnalyzer
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1174916
Files :
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/corelib/components/Form.java
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/FieldValidationSupportImpl.java
* /tapestry/tapestry5/trunk/tapestry-core/src/test/java/org/apache/tapestry5/internal/services/FieldValidationSupportImplTest.java
* /tapestry/tapestry5/trunk/tapestry-ioc/src/main/java/org/apache/tapestry5/ioc/util/ExceptionUtils.java
* /tapestry/tapestry5/trunk/tapestry-ioc/src/test/java/org/apache/tapestry5/ioc/util/ExceptionUtilsTest.java
* /tapestry/tapestry5/trunk/tapestry-ioc/src/test/java/org/apache/tapestry5/ioc/util/ExceptionWrapper.java
> 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