You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@wicket.apache.org by grazia <Gr...@gmail.com> on 2013/03/01 17:53:48 UTC

Re: Conflicting settings? isInputNullable and setConvertEmptyInputStringToNull ?

Has this been taken care of ? I have an AutoCompleteTextField that always
displays "null" even if I use the setConvertEmptyInputStringToNull (false).
In fact, the constructor of the autocomplete has it always set to true ...  



--
View this message in context: http://apache-wicket.1842946.n4.nabble.com/Conflicting-settings-isInputNullable-and-setConvertEmptyInputStringToNull-tp1885705p4656901.html
Sent from the Users forum mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org