...
For more information, checkout the LocalizationTextUtil LocalizedTextUtil class.
Examples
To display i18n text, you can use a call to getText() in the property tag, or any other tag such as the UI tags (this is especially useful for labels of UI tags):
Wiki Markup |
---|
{snippet:id=i18nExample|javadoc=true|lang=xml|url=com.opensymphony.webwork.components.Property} |
You may also use the text tag:
Wiki Markup |
---|
{snippet:id=i18nExample|javadoc=true|lang=xml|url=com.opensymphony.webwork.components.Text} |
Also, note that there is an i18n tag that will push a resource bundle on to the stack, allowing you to display text that would otherwise not be part of the resource bundle search hierarchy mentioned previously.
Wiki Markup |
---|
{snippet:id=i18nExample|javadoc=true|lang=xml|url=com.opensymphony.webwork.components.I18n} |
Warning |
---|
Internationalization in SiteMesh decorators is possible, but there are a few quirks about it. Check out the SiteMesh page to learn how to be integrate WebWork and SiteMesh, including integration tips. |
I18n Interceptor
See I18n Interceptorfor more info. It basically pushes a locale into the ActionContext map upon every request. Webwork (components, ActionSupport etc.) honours this and hence every i18n related aspect will used this locale. Its a pretty elegant way of changing locale upon request as well.
...