Description

WebWork supports internationalization (in short, i18n) in two different places: the UI tags and the action/field error messages.

• Tags Typically the i18n and text tag
• Validation

Resource Bundle Search Order

{snippet:id=searchorder|javadoc=true|url=com.opensymphony.xwork.util.LocalizedTextUtil}

For more information, checkout the LocalizedTextUtil class.

{snippet:id=packagenote|javadoc=true|url=com.opensymphony.xwork.util.LocalizedTextUtil}

Examples

Using getText()

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):

{snippet:id=i18nExample|javadoc=true|lang=xml|url=com.opensymphony.webwork.components.Property}

Text Tag

You may also use the text tag:

{snippet:id=i18nExample|javadoc=true|lang=xml|url=com.opensymphony.webwork.components.Text}

I18n Tag

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.

{snippet:id=i18nExample|javadoc=true|lang=xml|url=com.opensymphony.webwork.components.I18n}

I18n Interceptor

See I18n Interceptor for 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.

Global resource (webwork.custom.i18n.resources) in webwork.properties

{snippet:id=globalresource|javadoc=true|url=com.opensymphony.xwork.util.LocalizedTextUtil}

Comparison with Struts

{snippet:id=strutscomparison|javadoc=true|url=com.opensymphony.xwork.util.LocalizedTextUtil}