| « Wicket Javadocs in CHM format | Gently asking the GWT Hosted Mode to NOT redirect the logs » |
A quick post just to share a country list model I did a few days ago. It's no big deal, but I think it's worth sharing to avoid my fellow wicketeers the trouble to do it.
So, it's a standard Wicket Model that uses a standard ISO-3166-1 (2-char long) code to store the country name. The idea is to keep simplicity in my domain object, so the country property is just a String that stores the ISO3166 code. As it's not easily possible to use this ISO3166 code directly in a Wicket DropDownChoice (I want to display a localized country full name, but store the ISO-3166 short code), I had to create a Country object, which is internally used. Note however that the CountryList class provides an adaptor that converts this internally-used Country object into the property string of my domain POJO, so it's transparent.

The country list is localized, and comes from the ISO files I found at http://www.iso.org/iso/country_codes/iso_3166_code_lists.htm. Unfortunately, the ISO organization only provides english and french locales from the country name, so if you want more, you'll have to translate them yourselves and add the resource file to the jar.
Actually, using it is pretty straightforward, so I'll just show how to use it in an example.
The HTML is, as expected, the standard:
<select wicket:id="country"> <option value="US">United States</option> <option value="FR">France</option> </select>
The java code instanciates a country list, and uses it as a model for the DropDownChoice element (although it can be used with any component that uses an IModel<List> ).
CountryList countrylist = new CountryList(); // (1)
DropDownChoice country = new DropDownChoice("country",
countrylist.getAdaptor(new PropertyModel(this.obj, "country")), // (2)
countrylist, // (3)
countrylist.getRenderer()); // (4)
form.add(country);
in (1), we instantiate the CountryList class using the default constructor, which uses the Wicket Session locale. It is also possible to pass a Locale object to the constructor.
in (2), we use the adaptor provided by the CountryList class: this is a very basic IModel<Country> that takes a IModel<String> as its own model to set and get the correct Country element. This allows our POJO to just use a String property, instead of dealing with an annoying Country object.
in (3), this is actually the list of countries itself
in (4), this is the ChoiceRenderer that displays the full country names, instead of the short code.