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.
M
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 w
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" wrote:
Does anyone know of the best way to
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:
Then I call startUS so my validation.xml file is named
MyClass-startUS-validation.xml
Is this the best or rec
4 matches
Mail list logo
