[
https://issues.apache.org/jira/browse/WICKET-933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12999550#comment-12999550
]
Eric Hubert edited comment on WICKET-933 at 2/25/11 8:47 PM:
-------------------------------------------------------------
We also stumbled across this issue as our unique model values contained
negative numbers - thus no differentation between a real -1 and
NO_SELECTION_VALUE has been possible. We did not see a better option than
subclassing DropDownChoice (in our example) and overriding getModelValue() to
circumvent this "unwanted" behaviour.
It would be nice if you could adjust this for 1.5.
was (Author: ehubert):
We also stumbled accross this issue as our unique values contained negative
values - thus no differentation between a real -1 and NO_SELECTION_VALUE has
been possible. We did not see a better option than subclassing DropDownChoice
(in our example) and overriding getModelValue() to circumvent this "unwanted"
behaviour.
It would be nice if you could adjust this for 1.5.
> Look into removing AbstractSingleSelectChoice.NO_SELECTION_VALUE
> ----------------------------------------------------------------
>
> Key: WICKET-933
> URL: https://issues.apache.org/jira/browse/WICKET-933
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.3.0-final
> Reporter: Igor Vaynberg
>
> NO_SELECTION_VALUE is a very confusing thing. getmodelvalue() can sometimes
> return this value, when in fact it should return "" or null or whatever. we
> should look into removing NO_SELECTION_VALUE altogether. also see WICKET-635
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
