[MAGNOLIA-2923] Introducing ExceptionUtil Created: 30/Oct/09 Updated: 23/Jan/13 Resolved: 02/Nov/09 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | None |
| Fix Version/s: | 4.2 |
| Type: | New Feature | Priority: | Major |
| Reporter: | Magnolia International | Assignee: | Magnolia International |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Template: |
|
||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||
| Description |
|
One can do nice things with generics when handling exceptions. For instance, a method to unwrap exceptions of a certain type out of a RuntimeException could be handy with exception-less interface methods such as MgnlContext.SystemContextOperation() or ContentUtil.visit() |
| Comments |
| Comment by Magnolia International [ 30/Oct/09 ] |
|
Leaving open for discussion/ideas:
|
| Comment by Magnolia International [ 02/Nov/09 ] |
|
Keeping in info.magnolia.cms.util for now; see |