Mailing-List: contact issues-help@struts.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@struts.apache.org
Date: Thu, 9 Jan 2014 23:49:50 +0000 (UTC)
From: "Jose L Martinez-Avial (JIRA)" <jira@apache.org>
To: issues@struts.apache.org
Message-ID: <JIRA.12688164.1389311187287.72724.1389311390094@arcas>
In-Reply-To: <JIRA.12688164.1389311187287@arcas>
References: <JIRA.12688164.1389311187287@arcas>
Subject: [jira] [Updated] (WW-4274) DefaultActionInvocation  shows invalid
 log
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jose L Martinez-Avial updated WW-4274:
--------------------------------------

    Attachment: WW-4274.patch

> DefaultActionInvocation  shows invalid log
> ------------------------------------------
>
>                 Key: WW-4274
>                 URL: https://issues.apache.org/jira/browse/WW-4274
>             Project: Struts 2
>          Issue Type: Improvement
>          Components: Core Actions
>            Reporter: Jose L Martinez-Avial
>            Priority: Trivial
>         Attachments: WW-4274.patch
>
>
> The method invokeAction of com.opensymphony.xwork2.DefaultActionInvocation logs the following line for each action it executes:
> DEBUG com.opensymphony.xwork2.DefaultActionInvocation  - Executing action method = null
> I was curious about why the method was null, and find the following:
> {code:title=DefaultActionInvocation.java|borderStyle=solid}
>     protected String invokeAction(Object action, ActionConfig actionConfig) throws Exception {
>         String methodName = proxy.getMethod();
>         if (LOG.isDebugEnabled()) {
>             LOG.debug("Executing action method = " + actionConfig.getMethodName());
>         }
> [...]
> {code}
> but it does not use actionConfig.getMethodName() at all. It uses methodName, from proxy.getMethod(). And actionConfig.getMethodName() is null if no method was declared on the action definition (then it uses the standard execute). I believe that the log should be modified to show methodName instead if  actionConfig.getMethodName(). I'm sending attached a patch for this issue.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)