I'm not sure if it's bug in wicket. So your <input> is disabled, but
the TextField component is not? That's not good, you need to disable
the TextField too in that case.
-Matej
On 8/14/07, Alex Objelean <[EMAIL PROTECTED]> wrote:
>
> After migrating from wicket-1.2.6 to wicket-1.3.0-beta2 I had the following
> problem:
>
> application throws ConversionException when trying to convert a null value
> of the Textfield wich is disabled on the clientside.
>
> I've take a look on the convert() method of the FormComponent class and
> noticed the difference from the 1.2.x branch which may cause the issue:
>
> This snippet of code is from 1.3.0-beta2
> [CODE]
> if (typeName == null) {
> //string conversion code
> } else {
> //type conversion code
> }
> [/CODE]
>
> This snippet of code is from 1.2.6
> [CODE]
> if (type == null) {
> //string conversion code
> } else if (!Strings.isEmpty(getInput())) {
> //type conversion code
> }
> [/CODE]
>
> As you can see, in the 1.3.0-beta2 version, the conversion does not check if
> the getInput() is an empty string before performing type conversion. I
> wonder if it is a bug, or it is something that I missed?
>
> Thank you!
> Alex
> --
> View this message in context:
> http://www.nabble.com/Wicket-1.3-beta2-validation-%28conversion%29-bug--tf4265733.html#a12140062
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> 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]
