Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

Code Block
xml
xml
<ww:property value="getText('some.key')"/>

You may also use the text tag:

Code Block
xml
xml
<ww:text name="'some.key'"/>

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.

Code Block
xml
xml
<ww:i18n name="'some/package/bundle'">
    <ww:text name="'some.key'"/>
</ww: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.

...

Struts users should be familiar with the application.properties resource bundle, where you can put all the messages in the application that are going to be translated. WebWork2WebWork, though, splits the resource bundles per action or model class, and you may end up with duplicated messages in those resource bundles. A quick fix for that is to create a file called ActionSupport.properties in com/opensymphony/xwork and put it on your classpath. This will only work well if all your actions subclass ActionSupport.

...