You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Jose L Martinez-Avial (JIRA)" <ji...@apache.org> on 2014/01/06 17:31:50 UTC
[jira] [Created] (WW-4271) Improve loggign level in JSONUtil to
avoid excessive logs
Jose L Martinez-Avial created WW-4271:
-----------------------------------------
Summary: Improve loggign level in JSONUtil to avoid excessive logs
Key: WW-4271
URL: https://issues.apache.org/jira/browse/WW-4271
Project: Struts 2
Issue Type: Improvement
Components: Plugin - JSON
Affects Versions: 2.3.16
Reporter: Jose L Martinez-Avial
Priority: Trivial
Attachments: WW-4271.patch
The JSON result type generates excessive logs when used in debug mode, since it shows a log for each pattern defined in the result, and a log for the final result. For example:
DEBUG org.apache.struts2.json.JSONUtil - Adding include property expression: actionMessages.*
DEBUG org.apache.struts2.json.JSONUtil - Adding include property expression: actionResult
DEBUG org.apache.struts2.json.JSONUtil - Adding include property expression: data.*
DEBUG org.apache.struts2.json.JSONUtil - Adding include property expression: fieldErrors.*
DEBUG org.apache.struts2.json.JSONUtil - [JSON]{"actionMessages":[],"actionResult":"success","data":{},"fieldErrors":{}}
It would be better to change the level used in the method addPattern to trace, since in debug mode the final result is quite more useful than the "Adding include". I'm attaching a patch for this.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)