Red Hat

Developer Materials

jboss-logging-tools: Internationalization and Localization with JBoss Logging Tools

What is it?

The jboss-logging-tools quickstart demonstrates the use of JBoss Logging Tools in Red Hat JBoss Enterprise Application Platform. The logging tools create internationalized loggers, exceptions, and generic messages; and then provide localizations for them. This is done using a simple JAX-RS service. Translations in French(fr-FR), German(de-DE), and Swedish (sv-SE) are provided courtesy of for demonstration. My apologies if they are less than ideal translations.

Once the quick start is deployed you can access it using URLs documented below.

Instructions are included below for starting JBoss EAP with a different locale than the system default.

System requirements

The application this project produces is designed to be run on Red Hat JBoss Enterprise Application Platform 6.1 or later.

All you need to build this project is Java 6.0 (Java SDK 1.6) or later, Maven 3.0 or later.

Configure Maven

If you have not yet done so, you must Configure Maven before testing the quickstarts.


In the following instructions, replace EAP_HOME with the actual path to your JBoss EAP 6 installation. The installation path is described in detail here: Use of EAP_HOME and JBOSS_HOME Variables.

Configure the JBoss EAP Server to Start With a Different Locale (Optional)

To start the JBoss EAP server with a different locale than the system default:

  1. Make a backup copy of the EAP_HOME/bin/standalone.conf file.
  2. Edit the file and append commands to set the JVM parameters for the required country and language. Eg. Germany and German, DE and de.

     JAVA_OPTS="$JAVA_OPTS -Duser.language=de" This can be done as a single line if you prefer:
     JAVA_OPTS="$JAVA_OPTS -Duser.language=de"   

    Refer to

Start the JBoss EAP Server

  1. Open a command prompt and navigate to the root of the JBoss EAP directory.
  2. The following shows the command line to start the server:

     For Linux:   EAP_HOME/bin/
     For Windows: EAP_HOME\bin\standalone.bat

Build and Deploy the Quickstart

NOTE: The following build command assumes you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See Build and Deploy the Quickstarts for complete instructions and additional options.

  1. Make sure you have started the JBoss EAP server as described above.
  2. Open a command prompt and navigate to the root directory of this quickstart.
  3. Type this command to build and deploy the archive:

     mvn clean install jboss-as:deploy
  4. This will deploy target/jboss-logging-tools.war to the running instance of the server.

Access the application

The application will be running at the following URL: http://localhost:8080/jboss-logging-tools/

This landing page provides details and links to test the quickstart features. You can also directly access the following URLs.

  1. http://localhost:8080/jboss-logging-tools/rest/greetings/'name'
  2. http://localhost:8080/jboss-logging-tools/rest/greetings/'locale'/'name'
    • Example: http://localhost:8080/jboss-logging-tools/rest/greetings/fr-FR/Harold
    • Demonstrates how to obtain a message bundle for a specified locale and how to throw a localized exceptions. Note that the localized exception is a wrapper around WebApplicationException.
    • Returns a localized "hello name" string where name is the last component of the URL and the locale used is the one supplied in the locale URL.
    • Logs a localized "Hello message sent in locale" message using the JVM locale for the translation.
    • If the supplied locale is invalid (in this case if it contains more than 3 components, eg. fr-FR-POSIX-FOO), it throws a WebApplicationException (404) using a localizable sub-class of WebApplicationException.

      Note that WebApplicationException cannot be directly localized by JBoss Logging Tools using the @Message annotation due to the message parameter being ignored by the WebApplicationException constructors. Cases like this can be worked around by creating a subclass with a constructor that does deal with the message parameter.

  3. http://localhost:8080/jboss-logging-tools/rest/greetings/crashme
    • Demonstrates how to throw a localized exception with another exception specified as the cause. This is a completely contrived example.
    • Attempts to divide by zero, catches the exception, and throws the localized one.
  4. http://localhost:8080/jboss-logging-tools/rest/dates/daysuntil/'targetdate'
    • Example: http://localhost:8080/jboss-logging-tools/rest/dates/daysuntil/25-12-2020
    • Demonstrates how to pass parameters through to the constructor of a localized exception, and how to specify an exception as a cause of a log message.
    • Attempts to turn the targetdate URL component into a date object using the format dd-MM-yyyy
    • Returns number of days (as an integer) until that date
    • If the targetdate is invalid, for example, http://localhost:8080/jboss-logging-tools/rest/dates/daysuntil/31-02-2015:
      • Catches the ParseException
      • Creates a localized ParseException passing values from the caught exception as parameters to its constructor
      • Logs a localized message with the localized exception as the cause
      • Throws a WebApplicationException(400) with the text from the localized ParseException

Undeploy the Archive

  1. Make sure you have started the JBoss EAP server as described above.
  2. Open a command prompt and navigate to the root directory of this quickstart.
  3. When you are finished testing, type this command to undeploy the archive:

     mvn jboss-as:undeploy

Run the Quickstart in Red Hat JBoss Developer Studio or Eclipse

You can also start the server and deploy the quickstarts or run the Arquillian tests from Eclipse using JBoss tools. For general information about how to import a quickstart, add a JBoss EAP server, and build and deploy a quickstart, see Use JBoss Developer Studio or Eclipse to Run the Quickstarts

Debug the Application

If you want to debug the source code of any library in the project, run the following command to pull the source into your local repository. The IDE should then detect it.

  mvn dependency:sources

Recent Changelog

  • Mar 4, 2015(Sande Gilda):Bz1198744 Update README JBDS instructions to be more clear
  • Feb 3, 2015(Sande Gilda):Update the quickstart README files to point to the new shared EAP_HOME and Build and Deploy instructions
  • Jan 22, 2015(Sande Gilda):Bz1185085 Update README files to use full product name for JBDS
  • Dec 18, 2014(Sande Gilda):Bz1092026 Update README Target Product metadata value remove Product Versions metadata and make sure the full product name is near the top of the files
  • Nov 18, 2014(Sande Gilda):Bz1165075 Remove note about warnings in the log as the issue was resolved
  • Nov 6, 2014(Sande Gilda):Bz1160776 prepare for google search and fix typos
  • Oct 30, 2014(Sande Gilda):Bz1158059 Replace instances of JDBS with JBDS in README and links
  • Sep 30, 2014(Sande Gilda):Bz1144471 Remove Javadocs instructions as the requirement for Javadoc availability was dropped
  • Sep 24, 2014(Sande Gilda):Bz1146050 Add EAP 6.4 to the product version
  • Sep 24, 2014(Sande Gilda):Bz1146025 Fix issues with bean validation custom constraints README file. Also updated all README JDBS sections
Your Rating: