-
New Feature
-
Resolution: Won't Do
-
Major
-
None
-
4.3.8, 4.4.2
-
-
Empty show more show less
There are a few points in the Magnolia filter chain in which it would be really useful to be able to configure an exception handler, that can decide which exception should be rethrown, which can be "resolved" there and which can be just logged or simply ignored (if any).
First points that come to my mind are the rendering filter (expecially when using "strange" renderers, like spring, stripes or others), the cache filter (see MAGNOLIA-3566) and maybe the servlet filter (expecially when using "strange" servlets).
It would also be nice if the exception handling class could be injected by filter configuration.
I don't know if this is included in the refactoring that you are doing for magnolia 5 or not.
- is related to
-
MAGNOLIA-3566 Cache filter should ignore ClientAbortException
-
- Closed
-
-
MGNLCACHE-48 Cache filter should rethrow exceptions instead of wrapping them (at least when unrelated)
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- mentioned in
-
Wiki Page Loading...
