You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 28 Next »

Description

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

Resource Bundle Search Order

Error formatting macro: snippet: java.lang.NullPointerException

For more information, checkout the LocalizedTextUtil class.

Package Hierarchy

Error formatting macro: snippet: java.lang.NullPointerException

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

Error formatting macro: snippet: java.lang.NullPointerException

Text Tag

You may also use the text tag:

Error formatting macro: snippet: java.lang.NullPointerException

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.

Error formatting macro: snippet: java.lang.NullPointerException

 

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.

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

Error formatting macro: snippet: java.lang.NullPointerException

Comparison with Struts

Error formatting macro: snippet: java.lang.NullPointerException
  • No labels