Menu
▾
▴
springframework-rcp-dev
|
From: Geoffrey De S. (JIRA) <no...@at...> - 2007-04-19 08:29:30
|
An exception handling ChainPurger should replace evaluatedChainedIndex
----------------------------------------------------------------------
Key: RCP-470
URL: http://opensource.atlassian.com/projects/spring/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: 0.3.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://opensource.atlassian.com/projects/spring/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
|
From: Jan H. (JIRA) <no...@sp...> - 2008-03-18 07:22:07
|
[ http://jira.springframework.org/browse/RCP-470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan Hoskens updated RCP-470:
----------------------------
Fix Version/s: (was: 1.0.0)
1.0.1
> 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.1
>
>
> 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
|
|
From: Lieven D. (JIRA) <no...@sp...> - 2008-10-09 19:16:21
|
[ http://jira.springframework.org/browse/RCP-470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lieven Doclo updated RCP-470:
-----------------------------
Fix Version/s: (was: 1.0.1)
1.0.2
> 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.2
>
>
> 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
|
|
From: Lieven D. (JIRA) <no...@sp...> - 2008-10-09 19:49:18
|
[ http://jira.springframework.org/browse/RCP-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=40225#action_40225 ]
Lieven Doclo commented on RCP-470:
----------------------------------
Any ideas on this yet?
> 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.x
>
>
> 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
|
|
From: Lieven D. (JIRA) <no...@sp...> - 2008-10-09 19:49:19
|
[ http://jira.springframework.org/browse/RCP-470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lieven Doclo updated RCP-470:
-----------------------------
Fix Version/s: (was: 1.0.2)
1.x
> 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.x
>
>
> 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
|
|
From: Geoffrey De S. (JIRA) <no...@sp...> - 2008-10-10 18:04:27
|
[ http://jira.springframework.org/browse/RCP-470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Geoffrey De Smet resolved RCP-470.
----------------------------------
Resolution: Fixed
Fix Version/s: (was: 1.x)
1.0.0
Has already been fixed for 1.0.0, with the concept of an ExceptionPurger
> 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
|
|
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
|
Thanks for helping keep SourceForge clean.
X