You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Jasper Rosenberg (JIRA)" <ji...@apache.org> on 2015/03/20 16:02:38 UTC

[jira] [Closed] (WW-4480) DefaultActionInvocation.invokeAction calls unknownHandlerManager.handleUnknownMethod for any OgnlException

     [ https://issues.apache.org/jira/browse/WW-4480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jasper Rosenberg closed WW-4480.
--------------------------------
       Resolution: Duplicate
    Fix Version/s:     (was: 2.3.x)
                   2.3.22

Yup, that was it.

> DefaultActionInvocation.invokeAction calls unknownHandlerManager.handleUnknownMethod for any OgnlException
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: WW-4480
>                 URL: https://issues.apache.org/jira/browse/WW-4480
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Core Actions
>    Affects Versions: 2.3.20
>            Reporter: Jasper Rosenberg
>            Priority: Minor
>             Fix For: 2.3.22
>
>
> In our environment we are allowing method invocation exceptions in ognl to propagate. (This is so we can fail fast if someone tries to write code that invokes a static method)
> However, DefaultActionInvocation.invokeAction() does not distinguish between an OgnlException because of the method missing, and an OgnlException because the method threw an exception during execution. It calls handleUnknownMethod in both cases.  
> Instead of just checking for OgnlException it should only consider the method unknown if it is an ognl MethodFailedException and the cause is a java.lang.NoSuchMethodException



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)