[
https://issues.apache.org/struts/browse/WW-1717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_41474
]
James Holmes edited comment on WW-1717 at 7/17/07 10:10 AM:
------------------------------------------------------------
This was resolved in XWork ticket XW-542 which will be part of the 2.1 release
of XWork.
http://jira.opensymphony.com/browse/XW-542
was:
This was resolved in Xwork ticket XW-542 which will be part of 2.1 release of
XWork.
http://jira.opensymphony.com/browse/XW-542
> ParametersInterceptor - logging values that could not be applied to action
> properties
> -------------------------------------------------------------------------------------
>
> Key: WW-1717
> URL: https://issues.apache.org/struts/browse/WW-1717
> Project: Struts 2
> Issue Type: Improvement
> Affects Versions: 2.0.5
> Reporter: Dariusz Wojtas
> Assignee: James Holmes
> Priority: Minor
> Fix For: 2.1.0
>
>
> When I have some property that was kicked out by ParametersInterceptor as
> invalid, then it prints error message like this:
> 19:55:00,984 ERROR - ParametersInterceptor - ParametersInterceptor -
> [setParameters]: Unexpected Exception catched: Error setting expression
> 'myProp' with value '[Ljava.lang.String;@6d4f30'
> Can this be modified to support logging the exact values being skipped?
> Example:
> a) if the array contains single value: Error setting expression 'myProp'
> with value '<value>'
> a) array of size > 1: Error setting expression 'myProp' with value ['<1st
> value>', ... ]
> If this is a security reason not to print these values, then maybe it could
> be configurable via struts.properties, by default do not log exact values.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
