In order to make it easier to internationalize Java applications, the Java language offers a mechanism for centralizing all of the strings that a user might see. This is called a resource bundle and can be implemented in several ways as described later in the chapter. The application will use a key (for example, START_DATE_LABEL), and there will be a resource bundle for each supported language, thus mapping that key to the user interface string in that language.

JDeveloper is built for enterprise applications so that it automatically uses the resource bundles to prepare your application for localization. Let's take the XDM Common Model, shown in the following screenshot, as an example:

Now, watch what happens when we go into the Task entity object and define Control Hints for an attribute, as shown in the following screenshot:

As PersId is something that might be shown to the application end user, for example, as a prompt for a drop-down list, JDeveloper doesn...