this same key should still work in 1.2
in fact TypeValidator key would also work in 1.1, see http://www.wicket-wiki.org.uk/wiki/index.php/Validation_Messages
afaik the transition should have been seamless as we did not change this part of wicket.
i am wondering why it wasnt, can you provide more details?
-Igor
On 2/1/06, David Leangen <[EMAIL PROTECTED]> wrote:
> it looks like you declared one of your form components with a type,
> like new TextField("id", model, Integer.class);
> this by default adds a typevalidator to your form component.
Yes, exactly!
> the key you need to build is TypeValidator=message
> or fieldid.TypeValidator=message
Ok, that seemed to have worked, thank you!
BTW, this must be different from 1.1. In 1.1, I did not need to declare
a TypeValidator.
Shall I add it to the 1.2 migration page?
Cheers,
Dave
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
