I find things like this disturbing:
=== cut here ===
BeanValidatorForm: Validating ActionForm 'eddForm' using key
'AddBoxAction' for mapping '/AddBoxAction'
RequestProcessor: No errors detected, accepting input
=== cut here ===
If validator cannot not match key and mapping, should not it throw
took the leading "/" in validation.xml. Works like a charm now.
Thanks!
Niall Pemberton wrote:
If you use "setPathValidation(true)" it uses a key of the path name - with
the leading "/" stripped off. Either you need to specify the form name in
your validation.xml without the leading "/" - or in you
If you use "setPathValidation(true)" it uses a key of the path name - with
the leading "/" stripped off. Either you need to specify the form name in
your validation.xml without the leading "/" - or in your custom class
override the getValidationKey() method (rather than using the
setPathValidation
Hello All,
As the subject says I am having some trouble
trying to validate a LazyValidatorForm. Using the great examples
on the LazyValidatorForm page I created a custom class with
the required: setPathValidation(true) in the
constructor.
The Action path calling the form is "/AddBoxAction"
and vali
4 matches
Mail list logo
