Besides the 3-8 thing there (which I suppose is a typo), String
comparison with == works well for me:
<field-validator type="fieldexpression">
<param name="expression"><![CDATA[newPassword ==
verifNewPassword]]></param>
<message>Password must be the same</message>
</field-validator>
2008/8/15, natalia_ <[EMAIL PROTECTED]>:
>
> I want all validation on 2 fields to take place, I am not short-circuiting
> any. But it looks like the behavior is such that if stringlength fails the
> fieldexpression doesn't fire. Only if the field satisfies the length
> requirement then I see the result of fieldexpression to appear. I tried to
> put the fieldexpression before the stringlength, but that didn't change
> anything.
>
> <field name="account.loginName">
> <field-validator type="stringlength">
> 3
> 8
> <message key="validation.loginName.length">Login Name must be
> between ${minLength} and ${maxLength} characters in length</message>
> </field-validator>
>
> <field-validator type="fieldexpression">
>
> account.loginName.equals(confirmLoginName)
>
> <message key="validation.loginName.doNotMatch">Login Name and
> Confirm Login Name do not match</message>
> </field-validator>
>
> </field>
>
> <field name="confirmLoginName">
> <field-validator type="stringlength">
> 3
> 8
> <message key="validation.confirmLoginName.length">Confirm Login
> Name must be between ${minLength} and ${maxLength} characters in
> length</message>
> </field-validator>
> </field>
> --
> View this message in context:
> http://www.nabble.com/validation%3A-fieldexpression-doesn%27t-get-executed-if-stringlength-validation-fails-tp19004155p19004155.html
> Sent from the Struts - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
