You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pivot.apache.org by "Greg Brown (JIRA)" <ji...@apache.org> on 2010/04/29 14:07:54 UTC
[jira] Resolved: (PIVOT-483) better exception reporting for
BeanAdapter
[ https://issues.apache.org/jira/browse/PIVOT-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Greg Brown resolved PIVOT-483.
------------------------------
Resolution: Fixed
This is resolved. I didn't create the additional PropertyException class, but I did apply the other changes. The only reason I could see for adding the exception class would be so callers could explicitly catch it, and it doesn't seem like there is a strong use case for that. But let me know if you think otherwise.
I also changed getTargetException() to getCause() - see the Javadoc for this method:
http://java.sun.com/javase/6/docs/api/java/lang/reflect/InvocationTargetException.html#getTargetException()
> better exception reporting for BeanAdapter
> ------------------------------------------
>
> Key: PIVOT-483
> URL: https://issues.apache.org/jira/browse/PIVOT-483
> Project: Pivot
> Issue Type: Improvement
> Components: core-beans
> Affects Versions: 1.5.1
> Reporter: Dirk Moebius
> Priority: Minor
> Fix For: 1.5.1
>
> Attachments: pivot-483-better_exception_reporting.patch
>
>
> If BeanAdapter fails to get or set the value of a property for any reason (eg. wrong type, illegal argument exception etc.), the name of the property is not reported.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.