[
https://issues.apache.org/jira/browse/WICKET-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Vaynberg resolved WICKET-624.
----------------------------------
Resolution: Fixed
Fix Version/s: 1.3.0-beta2
> AbstractSingleChoice: components can't have specific null or nullValid
> messages
> -------------------------------------------------------------------------------
>
> Key: WICKET-624
> URL: https://issues.apache.org/jira/browse/WICKET-624
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.2.5
> Reporter: Charlie Dobbie
> Priority: Minor
> Fix For: 1.3.0-beta2
>
>
> AbstractSingleChoice, and thus DropDownChoice, accesses null and nullValid
> messages like this:
> final String option = getLocalizer().getString("nullValid", this, "");
> final String option = getLocalizer().getString("null", this, CHOOSE_ONE);
> So only the keys "null" and "nullValid" are checked in the relevant
> properties file. Wicket should provide for null/nullValid messages for
> specific components using the following keys:
> componentId.null
> componentId.nullValid
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
