To extend the standard PDI functionality, you may want to develop custom plugins. The instructions in this section address common extending scenarios, with each scenario having its own sample project. These folders of the sample code package contain sample projects. See the Get Started with the Sample PDI Project section of this guide to learn how to access the sample code.
Create Different Types of Plugins
Depending on what you want your plugin to do you may want to create one of any of the following types of plugins:
PDI uses property files for internationalization. Property files reside in the
messages sub-package in the plugin jar file. Each property file is specific to a locale. Property files contain translations for message keys that are used in the source code. A
messages sub-package containing locale-specific translations is called a message bundle.
Consider the package layout of the sample job entry plugin project. It contains its main Java class in the
org.pentaho.di.sdk.samples.jobentries.demopackage, and there is a message bundle containing the localized strings for the en_US locale.
Additional property files can be added using the naming pattern
messages_<locale>.properties. PDI core steps and job entries usually come with several localizations. See the shell job entry messages package for an example of more complete
Resolving Localized Strings
The key to resolving localized strings is to use the
getString() methods of
org.pentaho.di.i18n.BaseMessages. PDI follows conventions when using this class, which enables easy integration with the PDI translator tool.
All PDI plugin classes that use localization declare a private static
Class<?> PKG field, and assign a class that lives one package-level above the message bundle package. This is often the main class of the plugin.
PKG field defined, the plugin then resolves its localized strings with a call to
BaseMessages.getString(PKG, “localization key”, ... optional_parameters). The first argument helps PDI finding the correct message bundle, the second argument is the key to localize, and the optional parameters are injected into the localized string following the Java Message Format conventions.
Common Localization Strings
Some strings are commonly used,and have been pulled together into a common message bundle in
BaseMessages cannot find the key in the specified message bundle, PDI looks for the key in the common message bundle.
For an example, check the sample Job Entry plugin project, which uses this technique for localized string resolution in its dialog class.