[jsr339-experts] response filtering and exceptions
- From: Bill Burke <bburke@...>
- To: "jsr339-experts@..." <jsr339-experts@...>
- Subject: [jsr339-experts] response filtering and exceptions
- Date: Wed, 11 Jul 2012 10:28:16 -0400
I think we need something in ContainerResponseFilter to distinguish that
an exception was thrown from application code (and maybe internally as
well). Came across a user case recently that wanted to know that a
failure occured and what exact exception.
I suggest at minimum, 2 methods on ContainerResponseContext (better
names maybe?). Probably similar methods on WriterInterceptor.
Don't know, but maybe also a new method on ContainerResponseFilter
void failure(ContainerRequestContext requestContext,
failure should be called after any ExceptionMapper, but before anything
The main reason for this is name-bound filters and interceptors might
want to make a different decision based on a user failure.
JBoss, a division of Red Hat