This is a feature of JBuilder Professional and Enterprise.
The Resource Strings wizard prepares your application or applet for translation. It moves hardcoded strings in your source code files to ResourceBundles.
ResourceBundles are specialized files that contain a collection of translatable strings. (They may also contain other types of data, though this is less common.) A unique resource key identifies each translatable string in the ResourceBundle. The hardcoded string in your application is replaced by a reference to the ResourceBundle and the resource key. This separation of application logic and translatable elements is called resourcing. These separate resource files are then sent to translators.
The Resource Strings wizard supports the two standard forms of ResourceBundles: ListResourceBundle and PropertyResourceBundle.
PropertyResourceBundles are text files with a .properties extension, and are placed in the same location as the class files for the source code. ListResourceBundles are provided as Java source files. Because they are implemented as Java source code, new and modified ListResourceBundles need to be recompiled for deployment. With PropertyResourceBundles, there is no need for recompilation when translations are modified or added to the application. ListResourceBundles provide considerably better performance than PropertyResourceBundles.
To display this wizard,
The Resource Strings wizard has two steps.
continueButton.setLabel("Click to continue");In this example, the suggested key might be "continueButton.Label".
Selecting this option deselects the Generate Key From String Value option.
The Resource wizard lists all the strings it finds in your code in a table that contains these named columns.
There is a check box to the left of each row in the table. By default, it will be checked, meaning that the string will be resourced. If you don't want the string resourced, uncheck the check box for that row.
When you choose Finish, the wizard creates a ResourceBundle file and adds it to your project.