RE: Validator Formsets default vs Locale Specific-SOLVED

[Joe Hertz <jh...@speakeasy.net>]

As it happens-

You apparently CANNOT have a language specific validator rule for a property
that is not present in the default formset. You don't have to have any rules
for it, but it *must* be declared.



> -----Original Message-----
> From: Joe Hertz [mailto:jhertz@speakeasy.net] 
> Sent: Monday, November 01, 2004 8:43 PM
> To: 'Struts Users Mailing List'
> Subject: Validator Formsets default vs Locale Specific
> 
> The Struts Validator guide is pretty sparse on the subject.
> 
> What are the rules governing Default Formsets vs Locale 
> Specific Formsets (using Struts 1.2.4)?
> 
> To wit:
> 
> I have a Default Formset with validation rules for N forms. 
> I want also want language specific validations for one or 
> more of the N forms.
> 
> I would suspect that the way it should work is: 
> 
> If a language specific formset exists, and a validation rule 
> exists in it for the form being validated, it gets used. If 
> the language specific formset exists, but the form isn't 
> defined there, the rules for the form in the default formset 
> gets used.
> 
> I'm having a bear of a time trying to get my language 
> specific rules to get picked up. If a validation rule in the  
> default formset exists, it seems to "win".
> 
> I'm assuming that if a form exists in two places, there's no 
> inheritance on the property level. That is to say I can't 
> create a default formset and only define the ZipCode property 
> in the en-us validation rules. I'd have to define the entire 
> form in the en-us formset.
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
> 
> 
> 



---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org