I don't think that's how it works, but you might try storing masks etc. in
the resource file and accessing them via a %{zipValidationText} base action
property or something similar.I honestly don't remember how I implemented that, but I know I did it in two different ways and they both worked. Most useless help ever, I think. Dave On Wed, Jan 12, 2011 at 10:56 AM, Paul Mefford <[email protected]>wrote: > Maurizio, > > Thank you. I have read over that but I am interested in Localizing > the rules actually changing whether a field is required or not > depending on the country. For example I may have a County field for > my address which is required for the US but in Hong Kong they don't > require County. I was hoping that my setting the context locale I > would be able to get a different -validation.xml definition file. > > Paul > > On Tue, Jan 11, 2011 at 3:14 PM, Maurizio Cucchiara > <[email protected]> wrote: > > I strongly recommend you read the following link [1], in particoular the > > section that talks about "Localizing and Parameterizing Messages" > > > > [1] http://struts.apache.org/2.x/docs/validation.html > > > > Maurizio Cucchiara > > > > On Jan 11, 2011 7:27 PM, "Paul Mefford" <[email protected]> wrote: > > Does anyone know of the best way to have different validation rules > > for different locales in the validation.xml. > > > > I created what I feel is a hack by using wildcard in the alias: > > > > <action name="start*" class="com.MyClass" method="input"> > > > > Then I call startUS so my validation.xml file is named > > MyClass-startUS-validation.xml > > > > Is this the best or recommended way to do this? I thought there may be > > some -validation_en_US.xml or something but testing this doesn't work. > > > > --------------------------------------------------------------------- > > 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] > >
