This quick start demonstrates the use of JBoss Logging Tools to 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 http://translate.google.com 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.
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.
If you have not yet done so, you must Configure Maven before testing the quickstarts.
To start the JBoss server with a different locale than the system default:
Edit the file and append commands to set the JVM parameters for the required country and language.
Eg. Germany and German,
JAVA_OPTS="$JAVA_OPTS -Duser.country=DE" JAVA_OPTS="$JAVA_OPTS -Duser.language=de" This can be done as a single line if you prefer: JAVA_OPTS="$JAVA_OPTS -Duser.country=DE -Duser.language=de"
The following shows the command line to start the server:
For Linux: JBOSS_HOME/bin/standalone.sh For Windows: JBOSS_HOME\bin\standalone.bat
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.
Type this command to build and deploy the archive:
mvn clean install jboss-as:deploy
target/jboss-logging-tools.warto the running instance of the server.
The application will be running at the following URLs:
A landing page is found here that has a quick reference to the other URLs.
Demonstrates simple use of localised messages (with parameter) and logging.
name" string where
nameis the last component of the URL.
Demonstrates how to obtain a message bundle for a specified locale and how to throw a localised exceptions. Note that the localised exception is a wrapper around
name" string where
nameis the last component of the URL and the locale used is the one supplied in the
locale" message using the JVM locale for the translation
Throws a WebApplicationException (404) using a localizable sub-class of
Note that WebApplicationException cannot be directly localised by JBoss Logging Tools using the
@Message annotation due to the message parameter being ignored by
WebApplicationException's constructors. Cases like this can be worked around by creating a sub-class with a constructor that does deal with the message parameter.
Demonstrates throwing a localised exception with another exception specified as the cause. This is a completely contrived example.
Demonstrates how to pass parameters through to the constructor of a localised exception, and how to specify an exception as a cause of a log message.
targetdateURL component into a date object using the format
ParseExceptionpassing values from the caught exception as parameters to it's constructor
WebApplicationException(400) with the text from the localised
When you are finished testing, type this command to undeploy the archive:
You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see Use JBoss Developer Studio or Eclipse to Run the Quickstarts
If you want to debug the source code or look at the Javadocs of any library in the project, run either of the following commands to pull them into your local repository. The IDE should then detect them.
mvn dependency:sources mvn dependency:resolve -Dclassifier=javadoc