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.

the key you need to build is TypeValidator=message
or fieldid.TypeValidator=message

-Igor


On 2/1/06, David Leangen <[EMAIL PROTECTED]> wrote:

If this mail is out of order, I apologise. Something weird is happening
with my mails, and they are not being received in order... They're also
taking a long time to reach the list.

> It
> looks like it searching for a property named "TypeValidator" in your
> properties files which it doesn't find. Are you using any properties
> files? What is the message the user gets in 1.1 on providing a
> none-valid input?

No, message, since I was not using a validator.

I don't have a properties file, either.

I tried putting something in IndexPage.properties, but that didn't seem
to work:

<formId>.<fieldId>.TypeValidator=com.company.Validator


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

Reply via email to