[
https://issues.apache.org/jira/browse/WW-4530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14650148#comment-14650148
]
Alireza Fattahi commented on WW-4530:
-------------------------------------
ExceptionMappingInterceptor functionality is not enough always, so we have
developed an interceptor which handles exceptions. It means that the
ExceptionMappingInterceptor can be quite good in SOME actions. If
ExceptionMappingInterceptor supports MethodFilterInterceptor we can configure
it easily to work in conjunction with our exception handler.
Consider below which is a single web page web application:
We have developed an interceptor which always catch all exceptions and produce
a JSON result so all exception will be mapped to JSON string, with a predefined
key word like: {'error','it went wrong'}. The client always parse the string
and show an error message as a alert.
On the other hand, there are some actions which exception in them should be
forwarded to a global error page, this is where the ExceptionMappingInterceptor
with MethodFilterInterceptor can help us.
Please let me know if I need to explain it more.
> The ExceptionMappingInterceptor extends MethodFilterInterceptor
> ---------------------------------------------------------------
>
> Key: WW-4530
> URL: https://issues.apache.org/jira/browse/WW-4530
> Project: Struts 2
> Issue Type: Bug
> Reporter: Alireza Fattahi
> Fix For: 2.5
>
>
> Is it possible that the ExceptionMappingInterceptor extends
> MethodFilterInterceptor, this will help to add ExceptionMappingInterceptor
> to defined methods
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
