[
https://issues.apache.org/struts/browse/WW-1884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40897
]
Zach commented on WW-1884:
--------------------------
XWork 2.0.2 does not fix the problem for me. I still get the same problem and
the SEVERE Log still comes up:
Apr 24, 2007 10:07:31 PM org.apache.struts2.dispatcher.Dispatcher getSaveDir
INFO: Unable to find 'struts.multipart.saveDir' property setting. Defaulting to
javax.servlet.context.tempdir
Apr 24, 2007 10:07:31 PM
com.opensymphony.xwork2.interceptor.ParametersInterceptor setParameters
SEVERE: ParametersInterceptor - [setParameters]: Unexpected Exception catched:
Error setting expression 'categoryId' with value '[Ljava.lang.String;@157011e'
Apr 24, 2007 10:07:31 PM
com.opensymphony.xwork2.interceptor.ParametersInterceptor setParameters
SEVERE: ParametersInterceptor - [setParameters]: Unexpected Exception catched:
Error setting expression 'logoContentType' with value
'[Ljava.lang.String;@10a8143'
Apr 24, 2007 10:07:31 PM
com.opensymphony.xwork2.interceptor.ParametersInterceptor setParameters
SEVERE: ParametersInterceptor - [setParameters]: Unexpected Exception catched:
Error setting expression 'logoFileName' with value '[Ljava.lang.String;@ac8360'
Apr 24, 2007 10:07:31 PM
com.opensymphony.xwork2.interceptor.ParametersInterceptor setParameters
SEVERE: ParametersInterceptor - [setParameters]: Unexpected Exception catched:
Error setting expression 'photoContentType' with value
'[Ljava.lang.String;@1e534cb'
Apr 24, 2007 10:07:31 PM
com.opensymphony.xwork2.interceptor.ParametersInterceptor setParameters
SEVERE: ParametersInterceptor - [setParameters]: Unexpected Exception catched:
Error setting expression 'photoFileName' with value '[Ljava.lang.String;@ed3bff'
Apr 24, 2007 10:07:31 PM org.apache.struts2.interceptor.FileUploadInterceptor
intercept
INFO: Removing file logo
C:\eclipse\wkspc\.metadata\.plugins\org.eclipse.wst.server.core\tmp0\work\Catalina\localhost\whoda\upload_2e558e9d_11226b51165__8000_00000081.tmp
Apr 24, 2007 10:07:31 PM org.apache.struts2.interceptor.FileUploadInterceptor
intercept
> Validator Randomly Fails Valid Input
> ------------------------------------
>
> Key: WW-1884
> URL: https://issues.apache.org/struts/browse/WW-1884
> Project: Struts 2
> Issue Type: Bug
> Components: Actions, Interceptors
> Affects Versions: 2.0.6
> Environment: java version "1.6.0"
> Java(TM) SE Runtime Environment (build 1.6.0-b105)
> Java HotSpot(TM) Client VM (build 1.6.0-b105, mixed mode, sharing)
> struts2-core-2.0.6.jar
> struts2-tiles-plugin-2.0.6.jar
> xwork-2.0.1.jar
> Reporter: Zach
>
> On occasion, I'm receiving validation failures on valid input. Struts
> redirects to the form page and set's invalid input messages. I'm using only
> the required strings validations:
> @Validations(
> requiredStrings = {
> @RequiredStringValidator(type =
> ValidatorType.SIMPLE, fieldName = "req", message = "msg", shortCircuit =
> true, trim = true)
> }
> )
> I think the error is caused by an exception:
> Apr 15, 2007 10:08:49 AM com.opensymphony.xwork2.util.OgnlUtil
> internalSetProperty
> WARNING: Caught OgnlException while setting property 'methodName' on type
> 'com.opensymphony.xwork2.validator.validators.RequiredStringValidator'.
> ognl.NoSuchPropertyException:
> com.opensymphony.xwork2.validator.validators.RequiredStringValidator.methodName
> at
> ognl.ObjectPropertyAccessor.setProperty(ObjectPropertyAccessor.java:132)
> at
> com.opensymphony.xwork2.util.OgnlValueStack$ObjectAccessor.setProperty(OgnlValueStack.java:68)
> at ognl.OgnlRuntime.setProperty(OgnlRuntime.java:1656)
> at ognl.ASTProperty.setValueBody(ASTProperty.java:101)
> at ognl.SimpleNode.evaluateSetValueBody(SimpleNode.java:177)
> at ognl.SimpleNode.setValue(SimpleNode.java:246)
> ...
> I would be willing to bet this has already been logged, and probably fixed,
> but I can't find a bug logged in this system that says it has. I also tried
> to build the latest trunk this morning, but maven reported 11 Test errors and
> would not complete the build. I apologize if the fix is already out there,
> but I'm logging this in case this is a new 2.0.6 issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
