Dinesh on Java

Struts2

Internationalization and Localization in struts2

Internationalization (i18n) is the process of planning and implementing products and services so that they can easily be adapted to specific local languages and cultures, a process called localization. The internationalization process is sometimes called translation or localization enablement. Internationalization is abbreviated i18n because the word starts with an i and ends with an n, and there are 18 characters between the first i and the last n.

Will create a simple employee form screen, display the message from resource bundle via the Struts 2 UI components, and change the locale base on the selected language option.

Resource Bundles:

uses resource bundles to provide multiple language and locale options to the users of the web application. You don’t need to worry about writing pages in different languages. All you have to do is to create a resource bundle for each language that you want. The resource bundles will contain titles, messages, and other text in the language of your user. Resource bundles are the file that contains the key/value pairs for the default language of your application.

When you reference a message element by its key, Struts framework searches for a corresponding message bundle in the following order:

ActionClass.properties
Interface.properties
SuperClass.properties
model.properties
package.properties
struts.properties
global.properties

To develop your application in multiple languages, you would have to maintain multiple property files corresponding to those languages/locale and define all the content in terms of key/value pairs.

For example if you are going to develop your application for US English (Default), Hindi,Spanish, Chinese, German and Franch the you would have to create three properties files. Here I will use global.properties file only, you can make use of different property files to segregate different type of messages.

global.properties: By default English (United States) will be applied
global_fr.properties: This will be used for Franch locale.
global_es.properties: This will be used for Spanish locale.
global_de.properties: This will be used for German locale.
global_hn.properties: This will be used for Hindi locale.
global_zh_CN.properties: This will be used for China locale.

global.properties:

global.name = Name
global.age = Age
global.telephone = Telephone
global.email = Email
global.submit = Submit
global.success = Employee Successfully Added
global.form = Employee Form

global_hn.properties:

global.name = u0928u093Eu092E
global.age = u0909u092Eu094Du0930
global.telephone = u091Fu0947u0932u0940u092Bu094Bu0928
global.email = u0908u092Eu0947u0932
global.submit = u092Au094Du0930u0938u094Du0924u0941u0924 u0915u0930u0928u093E
global.success = u0915u0930u094Du092Eu091Au093Eu0930u0940 u0938u092Bu0932u0924u093Eu092Au0942u0930u094Du0935u0915 u091Cu094Bu0921u093Cu093E u0917u092Fu093E
global.form = u0915u0930u094Du092Eu091Au093Eu0930u0940 u092Au0930u094Du091Au093E

global_de.properties:

global.name = Nennen
global.age = Alter
global.submit = Einreichen
global.form = Angestellter Formular
global.telephone = Telefonieren
global.email = Emaeiln
global.success = Mitarbeiter erfolgreich am

global_es.properties:

global.name = Nombre de usuario
global.age = Edad
global.telephone = Teléfono
global.email = Emaile
global.submit = Presentar
global.form = Formulario Empleado
global.success = Empleado con éxito Agregado

global_fr.properties:

global.name = Nom d'utilisateur 
global.age = l'âge
global.telephone = téléphone
global.email = Emailé
global.submit = Soumettre des
global.form = Formulaire d'employés
global.success = Employé ajouté avec succès

global_zh_CN.properties:

global.name = u540D
global.age =u5E74u9F84
global.telephone = u7535u8BDD
global.email = u7535u5B50u90AEu4EF6
global.submit=u63d0u4ea4
global.form = u5458u5DE5u8868u5355
global.success = u5458u5DE5u6210u529Fu6DFBu52A0

Access the messages:

There are several ways to access the message resources, including getText, the text tag, key attribute of UI tags, and the i18n tag. Let us see them in brief:

To display i18n text, use a call to getText in the property tag, or any other tag, such as the UI tags as follows:

<s:property value="getText('some.key')" />

The text tag retrieves a message from the default resource bundle ie. struts.properties

<s:text name="some.key" />

The i18n tag pushes an arbitrary resource bundle on to the value stack. Other tags within the scope of the i18n tag can display messages from that resource bundle:

<s:i18n name="some.package.bundle">
     <s:text name="some.key" />
</s:i18n>

The key attribute of most UI tags can be used to retrieve a message from a resource bundle:

<s:textfield key="some.key" name="textfieldName"/>

Localization Example:

Let us target to create employee.jsp from the previous chapter in multiple languages. Same file would be written as follows:

<%@ page contentType="text/html; charset=UTF-8"%>
<%@ taglib prefix="s" uri="/struts-tags"%>
<html>
<head>
<title><s:property value="getText('global.form')" /> - Struts2 Demo | dineshonjava.com</title>
<s:head />
</head>
 
<body>
<h2><s:property value="getText('global.form')" /></h2>
 
<s:form action="employee" method="post" validate="true">
    <s:textfield name="name" key="global.name" size="20" />
    <s:textfield name="age" key="global.age" size="20" />
    <s:textfield name="email" key="global.email" size="20" />
    <s:textfield name="telephone" key="global.telephone" size="20" />
    <s:submit name="submit" key="global.submit" align="center" />
</s:form>

<s:url id="localeEN" namespace="/" action="locale" >
   <s:param name="request_locale" >en</s:param>
</s:url>
<s:url id="localeHN" namespace="/" action="locale" >
   <s:param name="request_locale" >hn</s:param>
</s:url>
<s:url id="localeES" namespace="/" action="locale" >
   <s:param name="request_locale" >es</s:param>
</s:url>
<s:url id="localezhCN" namespace="/" action="locale" >
   <s:param name="request_locale" >zh_CN</s:param>
</s:url>
<s:url id="localeDE" namespace="/" action="locale" >
   <s:param name="request_locale" >de</s:param>
</s:url>
<s:url id="localeFR" namespace="/" action="locale" >
   <s:param name="request_locale" >fr</s:param>
</s:url>
 
<s:a href="%{localeEN}" >English</s:a>
<s:a href="%{localeHN}" >Hindi</s:a>
<s:a href="%{localeES}" >Spanish</s:a>
<s:a href="%{localezhCN}" >Chinese</s:a>
<s:a href="%{localeDE}" >German</s:a>
<s:a href="%{localeFR}" >France</s:a>
</body>
</html>

We will create success.jsp file which will be invoked in case defined action returns SUCCESS.

<%@ page contentType="text/html; charset=UTF-8"%>
<%@ taglib prefix="s" uri="/struts-tags"%>
<html>
<head>
<title><s:property value="getText('global.form')" /> - Struts2 Demo | dineshonjava.com</title>
</head>
 
<body>
    <h2><s:property value="getText('global.success')" />.</h2>
</body>
</html>

Here we would need to create following two actions.

(a) First action a to take care of Locale and display same success.jsp file with different language
(b) Another action is to take care of submitting form itself.
Both the actions will return SUCCESS, but we will take different actions based on return values because our purpose is different for both the actions:

EmployeeLocaleAction.java

package com.dineshonjava.com.struts2.action.locale;

import com.opensymphony.xwork2.ActionSupport;

/**
 * @author Dinesh Rajput
 *
 */
public class EmployeeLocaleAction extends ActionSupport {

 private static final long serialVersionUID = 1L;
     
    public String execute() {
        return SUCCESS;
    }
}

EmployeeAction.java

package com.dineshonjava.com.struts2.action;

import com.opensymphony.xwork2.ActionSupport;

/**
 * @author Dinesh Rajput
 *
 */
public class EmployeeAction extends ActionSupport {

 private static final long serialVersionUID = 1L;
 private String name;
    private Integer age;
    private String email;
    private String telephone;
    
    public String addEmployee() {
        return SUCCESS;
    }
 public String getName() {
  return name;
 }
 public void setName(String name) {
  this.name = name;
 }
 public Integer getAge() {
  return age;
 }
 public void setAge(Integer age) {
  this.age = age;
 }
 public String getEmail() {
  return email;
 }
 public void setEmail(String email) {
  this.email = email;
 }
 public String getTelephone() {
  return telephone;
 }
 public void setTelephone(String telephone) {
  this.telephone = telephone;
 }
}

We will create our struts.xml with two actions as follows:

<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE struts PUBLIC
    "-//Apache Software Foundation//DTD Struts Configuration 2.0//EN"
    "http://struts.apache.org/dtds/struts-2.0.dtd">
 
<struts>
    <constant name="struts.enable.DynamicMethodInvocation" value="false" />
    <constant name="struts.devMode" value="false" />
    <constant name="struts.custom.i18n.resources" value="global" />
 
    <package name="default" extends="struts-default" namespace="/">
        <action name="employee" class="com.dineshonjava.com.struts2.action.EmployeeAction">
            <result name="success">/success.jsp</result>
      <result name="input">/employee.jsp</result>
          <result name="error">/error.jsp</result>
        </action>
        
        <action name="locale" class="com.dineshonjava.com.struts2.action.locale.EmployeeLocaleAction">
            <result name="success">/employee.jsp</result>
        </action>
    </package>
  
</struts>

Following is the content of web.xml file:

<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd" id="WebApp_ID" version="3.0">
  <display-name>Struts2I18N</display-name>
 <filter>
        <filter-name>struts2</filter-name>
        <filter-class>
            org.apache.struts2.dispatcher.FilterDispatcher
        </filter-class>
    </filter>
    <filter-mapping>
        <filter-name>struts2</filter-name>
        <url-pattern>/*</url-pattern>
    </filter-mapping>
    <welcome-file-list>
        <welcome-file>index.jsp</welcome-file>
    </welcome-file-list>
</web-app>

Now, right click on the project name and click Export > WAR File to create a War file. Then deploy this WAR in the Tomcat’s webapps directory. Finally, start Tomcat server and try to access
URL http://localhost:8080/doj/employee.jsp.

This will give you following screen:

Now select on Hindi language.
http://localhost:8080/doj/locale.action?request_locale=hn

Now select on Spanish language.
http://localhost:8080/doj/locale.action?request_locale=es

Now select on Chines language.
http://localhost:8080/doj/locale.action?request_locale=zh_CN

Now select on German language.
http://localhost:8080/doj/locale.action?request_locale=de

Now select on German language.
http://localhost:8080/doj/locale.action?request_locale=fr

Now after submit the form following success messages display as per as languages selected.

Download Source Code
Struts2I18N.zip

<<Previous << || Index || >>Next >>

Dinesh Rajput

Dinesh Rajput is the chief editor of a website Dineshonjava, a technical blog dedicated to the Spring and Java technologies. It has a series of articles related to Java technologies. Dinesh has been a Spring enthusiast since 2008 and is a Pivotal Certified Spring Professional, an author of a book Spring 5 Design Pattern, and a blogger. He has more than 10 years of experience with different aspects of Spring and Java design and development. His core expertise lies in the latest version of Spring Framework, Spring Boot, Spring Security, creating REST APIs, Microservice Architecture, Reactive Pattern, Spring AOP, Design Patterns, Struts, Hibernate, Web Services, Spring Batch, Cassandra, MongoDB, and Web Application Design and Architecture. He is currently working as a technology manager at a leading product and web development company. He worked as a developer and tech lead at the Bennett, Coleman & Co. Ltd and was the first developer in his previous company, Paytm. Dinesh is passionate about the latest Java technologies and loves to write technical blogs related to it. He is a very active member of the Java and Spring community on different forums. When it comes to the Spring Framework and Java, Dinesh tops the list!