[WICKET-624] AbstractSingleChoice: components can't have specific null or nullValid messages

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.2.5
• Fix Version/s: 1.3.0-beta2
• Component/s: wicket
• Assignee: Unassigned
• Reporter: Charlie Dobbie
• Created: 07/Jun/07 13:31
• Updated: 07/Jun/07 13:35
• Resolved: 07/Jun/07 13:35

Description

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