[WW-1884] Validator Randomly Fails Valid Input

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.6
• Fix Version/s: 2.0.8
• Component/s: Core Actions, Core Interceptors

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

• Flags: Important
• Assignee: Rainer Hermanns
• Reporter: Zach
• Created: 15/Apr/07 15:13
• Updated: 28/Oct/12 22:11
• Resolved: 18/May/07 16:25

Description

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.