|
From: Geoffrey De S. (JIRA) <no...@sp...> - 2008-10-10 18:06:26
|
[ http://jira.springframework.org/browse/RCP-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=40254#action_40254 ]
Geoffrey De Smet commented on RCP-470:
--------------------------------------
see manual btw, it explains it :)
> An exception handling ChainPurger should replace evaluatedChainedIndex
> ----------------------------------------------------------------------
>
> Key: RCP-470
> URL: http://jira.springframework.org/browse/RCP-470
> Project: Spring Framework Rich Client Project
> Issue Type: New Feature
> Components: Application Framework
> Reporter: Geoffrey De Smet
> Assignee: Geoffrey De Smet
> Fix For: 1.0.0
>
>
> evaluatedChainedIndex only applies to MessagesDialogExceptionHandler, but it should also be useable on the delegating exception handler.
> evaluatedChainedIndex is to clumsy in most circumstances as it's the type of the exceptions, instead of the level that decide if it should be evaluated.
> ExceptionChainPurger to the rescue, pluggable into any ExceptionHandler.
> It cuts the first part of an exception chain if needed.
> It contains 2 properties:
> - alwaysEvaluatePrioritizedList: List<Class<? extends Exception>>: for example it contains "SQL504Exception", then any chain which contains that type of exception will be evaluated as the SQL504Exception instance.
> - alwaysTryToUnwrapList: List<Class<? extends Exception>>: for example it contains "WrappingServiceException", so it always tries to unwrap that.
> TODO: find beter names, suggestions welcome.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|