The problem with custom resource bundle loading is that Designer does not know where to find the resource files so that it can render the widgets in different languages or edit the resource files when you edit the UI.
The parser has built-in support for the various standard internationalization patterns so it can find resource bundles references using any of those common patterns.
In order to support custom resource bundle loading, we have added support for a new, custom @wbp.nls.resourceBundle
JavaDoc tag in the latest build that will tell the parser where to find the resource files. For example...
- Code: Select all
* @wbp.nls.resourceBundle test.messages
private static final ResourceBundle m_bundle = MyResourceBundleFactory.getMainBundle();
...where "test.messages" is the name of the resource file for the default locale.