> i dont think this is needed. your custom converter should include a null
> check.
>
But I do not use custom converter. In my case it is about a simple String or
Integer or whatever...
So, you suggest to create a custom converter for each case where I disable
the form component on the server-side?
Also, keeping in sync client-side with server-side, means that I need to
make an ajax round-trip just to update the field disable state on the
server.. IMO it is unnecessary overhead.
Maybe we can find a compromise regarding this issue?
--
View this message in context:
http://www.nabble.com/Wicket-1.3-beta2-validation-%28conversion%29-bug--tf4265733.html#a12342815
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
