[prev in list] [next in list] [prev in thread] [next in thread] 

List:       struts-dev
Subject:    [jira] [Commented] (WW-3880) Silent refusal of parameters without any logging
From:       "Hudson (JIRA)" <jira () apache ! org>
Date:       2012-09-26 22:21:07
Message-ID: 1433005119.131017.1348698068005.JavaMail.jiratomcat () arcas
[Download RAW message or body]


    [ https://issues.apache.org/jira/browse/WW-3880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13464242#comment-13464242 \
] 

Hudson commented on WW-3880:
----------------------------

Integrated in Struts2 #534 (See [https://builds.apache.org/job/Struts2/534/])
    WW-3880 adds logging when parameter wasn't accepted (Revision 1390696)

     Result = FAILURE
lukaszlenart : 
Files : 
* /struts/struts2/trunk/xwork-core/src/main/java/com/opensymphony/xwork2/interceptor/ParametersInterceptor.java


                
> Silent refusal of parameters without any logging
> ------------------------------------------------
> 
> Key: WW-3880
> URL: https://issues.apache.org/jira/browse/WW-3880
> Project: Struts 2
> Issue Type: Improvement
> Components: Core Interceptors
> Affects Versions: 2.3.1.2, 2.3.3, 2.3.4, 2.3.4.1
> Reporter: Tom Briers
> Assignee: Lukasz Lenart
> Priority: Minor
> Fix For: 2.3.5
> 
> 
> In version 2.3.4.1 a check on the length of the name has been added in the \
> com.opensymphony.xwork2.interceptor.ParametersInterceptor class.  If the size of \
> the name exceeds the set value, the parameter is silently refused without any hint \
> of what happened. The same problem exists with the other checks to accept a \
> parameter. Is it possible to add a logging when devMode is active so possible \
> issues can be identified more easily.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[prev in list] [next in list] [prev in thread] [next in thread]