In this article we will explain how to customize the default EBX messages, by creating a new locale.

Documentation

In order to add a new locale, the following steps must be followed:

• Declare the new locale in the EBX™ main configuration file.

For example: ebx.locales.available=en-US, fr-FR, xx
See Configuring EBX™ localization.

• Deploy the following files in the EBX™ class-path:

•  A formatting policy file, named com.orchestranetworks.i18n.frontEndFormattingPolicy_xx.xml,
•  A set of localized message files (*_xx.mxml) in a resource bundle.

Note: The files must be ending with ".mxml".

A complete template set of files is available here.

Example

I want to create a new locale: en-ZA that will extend the default english locale and modify the default primary key message: "The requested operation has failed. Reason: Cannot create the new record since its primary key is already used."

It is located in addErrorCannotCreateSincePrimaryKeyUsed in uowPrinter_xx.mxml.

The files I will use and modify are:

• frontEndFormattingPolicy_xx.xml
• uowPrinter_xx.mxml

I then have to deploy the files as a JAR, alongside ebx.jar, respecting the following tree:

My locale with its custom message is now created.