My fault i use a internal boolean to check, but used the inversed
condition before adding the error.
It is working now.
Raphaël
Raphaël Piéroni a écrit :
Grzegorz Kossakowski a écrit :
Raphaël Piéroni pisze:
Thanks for the answer.
Is this functionnality avaliable in 1.0.0-RC1 ? It seems not.
When that new version wil be released ?
As I pointed out, Spring-based Forms will be released as 1.1.0. I don't know
what are current plans
and if there any show-stoppers for 1.1.0's first milestone release. I guess
it's better to ask on
dev list. Hint: usually pleasant bugging developers to push the release can
give good result. ;)
Meanwhile having the springified validator, i added them myself in the
flowscript
like in :
var form = new Form("view/user/create.cform");
var validator = spring.getBean("createUserValidator");
form.lookupWidget('userName').addValidator(validator);
form.lookupWidget('unixLogin').addValidator(validator);
In the validator i do :
ValidationError error = new
ValidationError("error.createUser.userName", true);
((Field) widget).setValidationError(error);
return false;
I saw (using logs) that the validation is false (which is what i test)
But the form completes as if it was validated.
Raphaël
Anyway, you can still develop Avalon-based validator using 1.0.0-RC1 version of
Forms. The choice is
yours.
---------------------------------------------------------------------
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]
