You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "zhouyanming (JIRA)" <ji...@apache.org> on 2009/04/24 10:59:30 UTC
[jira] Created: (WW-3096) change log level from "warn" to "debug"
in org.apache.struts2.components.ServletUrlRenderer
change log level from "warn" to "debug" in org.apache.struts2.components.ServletUrlRenderer
-------------------------------------------------------------------------------------------
Key: WW-3096
URL: https://issues.apache.org/struts/browse/WW-3096
Project: Struts 2
Issue Type: Improvement
Reporter: zhouyanming
we are not always only use struts2,sometimes need use spring action process,like <s2:form action="/thisisspringaction">
so change
if (namespace != null) {
LOG.warn("No configuration found for the specified action: '" + actionName + "' in namespace: '" + namespace + "'. Form action defaulting to 'action' attribute's literal value.");
}
to
if (namespace != null && LOG.isDebugEnabled())) {
LOG.debug("No configuration found for the specified action: '" + actionName + "' in namespace: '" + namespace + "'. Form action defaulting to 'action' attribute's literal value.");
}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WW-3096) change log level from "warn" to "debug"
in org.apache.struts2.components.ServletUrlRenderer
Posted by "Dave Newton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-3096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46106#action_46106 ]
Dave Newton commented on WW-3096:
---------------------------------
Why not just turn down the log level for ServletUrlRenderer?
I'm not sure I'd vote for turning this down in the source; this is a relatively unusual use-case for which there is a workaround: most people writing S2 apps will want to be warned, as it's almost always something wrong in their configuration.
> change log level from "warn" to "debug" in org.apache.struts2.components.ServletUrlRenderer
> -------------------------------------------------------------------------------------------
>
> Key: WW-3096
> URL: https://issues.apache.org/struts/browse/WW-3096
> Project: Struts 2
> Issue Type: Improvement
> Reporter: zhouyanming
>
> we are not always only use struts2,sometimes need use spring action process,like <s2:form action="/thisisspringaction">
> so change
> if (namespace != null) {
> LOG.warn("No configuration found for the specified action: '" + actionName + "' in namespace: '" + namespace + "'. Form action defaulting to 'action' attribute's literal value.");
> }
> to
> if (namespace != null && LOG.isDebugEnabled())) {
> LOG.debug("No configuration found for the specified action: '" + actionName + "' in namespace: '" + namespace + "'. Form action defaulting to 'action' attribute's literal value.");
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (WW-3096) change log level from "warn" to "debug" in
org.apache.struts2.components.ServletUrlRenderer
Posted by "Dave Newton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-3096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dave Newton closed WW-3096.
---------------------------
Resolution: Not A Problem
I don't know; have you considered reading the Java logging and/or GAE documentation? Closing issue; if anybody thinks the logging level should be changed feel free to patch but I think it's appropriate as-is.
> change log level from "warn" to "debug" in org.apache.struts2.components.ServletUrlRenderer
> -------------------------------------------------------------------------------------------
>
> Key: WW-3096
> URL: https://issues.apache.org/struts/browse/WW-3096
> Project: Struts 2
> Issue Type: Improvement
> Reporter: zhouyanming
>
> we are not always only use struts2,sometimes need use spring action process,like <s2:form action="/thisisspringaction">
> so change
> if (namespace != null) {
> LOG.warn("No configuration found for the specified action: '" + actionName + "' in namespace: '" + namespace + "'. Form action defaulting to 'action' attribute's literal value.");
> }
> to
> if (namespace != null && LOG.isDebugEnabled())) {
> LOG.debug("No configuration found for the specified action: '" + actionName + "' in namespace: '" + namespace + "'. Form action defaulting to 'action' attribute's literal value.");
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WW-3096) change log level from "warn" to "debug"
in org.apache.struts2.components.ServletUrlRenderer
Posted by "zhouyanming (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-3096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46140#action_46140 ]
zhouyanming commented on WW-3096:
---------------------------------
I'm use java.util.logging in google appengine,how to turn down this log?
> change log level from "warn" to "debug" in org.apache.struts2.components.ServletUrlRenderer
> -------------------------------------------------------------------------------------------
>
> Key: WW-3096
> URL: https://issues.apache.org/struts/browse/WW-3096
> Project: Struts 2
> Issue Type: Improvement
> Reporter: zhouyanming
>
> we are not always only use struts2,sometimes need use spring action process,like <s2:form action="/thisisspringaction">
> so change
> if (namespace != null) {
> LOG.warn("No configuration found for the specified action: '" + actionName + "' in namespace: '" + namespace + "'. Form action defaulting to 'action' attribute's literal value.");
> }
> to
> if (namespace != null && LOG.isDebugEnabled())) {
> LOG.debug("No configuration found for the specified action: '" + actionName + "' in namespace: '" + namespace + "'. Form action defaulting to 'action' attribute's literal value.");
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.