How-to guides
Directions for a specific goal.
- Translate component texts Move the texts of a page or panel into properties files, show them with wicket:message or from Java, and let the user switch the language.
- Put model values into translated texts Show translated texts through ResourceModel and StringResourceModel, fill in property values and MessageFormat parameters, and choose the key from the data.
- Translate the options of a choice Show translated options in a DropDownChoice, RadioChoice or other choice component, translate enum values, and change the "Choose One" text.
- Load texts from your own source Add a string resource loader that reads texts from a database or an existing Java ResourceBundle, and change the chain of loaders Wicket searches.
Reference
The classes, tags and settings, described.
- Where Wicket looks for texts The exact order in which Wicket searches resource bundles for a key, the file names it tries, and the settings that change the search.
Explanation
Why Wicket works the way it does.
- How Wicket localizes Where the locale of a page comes from, why texts live in properties files next to the components that use them, and why the page can override its panels.