[
https://issues.apache.org/jira/browse/WICKET-933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timo Rantalaiho updated WICKET-933:
-----------------------------------
Fix Version/s: (was: 1.4-M4)
1.5-M1
I think that the constant NO_SELECTION_VALUE might be a good name to indicate
that nothing is selected, but returning -1 as the model object value is
definitely strange :)
Anyway, as this changes existing behavior, it's better to only fix this in 1.5,
right? It's not exactly a bug and there are no votes nor watchers.
> 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
> Fix For: 1.5-M1
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
