The information on this page assumes you have already read Unblu Server i18n Configuration.
In addition to the standard localized text settings mechanisms described in Unblu Server i18n Configuration, unblu has a set of additional localized text settings features that allow for more complex and dynamic setups.
Dynamic reconfiguration must be triggered explicitly by calling the /sys-unblu/rest/propertyCascade/reload rest service. If your server is running on localhost on port 8080, you need to request http://localhost:8080/sys-unblu/rest/propertyCascade/reload to trigger dynamic reconfiguration. CAUTION: make sure the /sys-unblu path is properly protected (see security considerations).
Dynamic reconfiguration also works for configuration settings (see Unblu Server Configuration and Advanced Unblu Server Configuration).
Instead of using a single localized text file, it is also possible to split localized text in multiple files. Multiple localized text files are specified using a coma separated list of file path or urls in the "com.unblu.textoverlay" configuration setting instead of a single value (see using localized text configuration files).
This example specifies two localized text files: http://configurationserver/unblu/unblu-text.com and /opt/unblu/unblu-text.properties.
When using multiple localized text files, the ones that are defined later will always win over the ones defined earlier.
In the example above this means that properties defined in /opt/unblu/unblu-text.properties will win over properties defined in http://configurationserver/unblu/unblu-text.properties.
Using multiple localized text files can make sense for instance in an unblu cluster where servers share some but not all of the settings. A second scenario for using multiple localized text files is when there are multiple environments (i.e. prod, stage, development) that share most of the localized text settings but still need some individual configuration.
Usually localized properties are global to the unblu server, this means that a localized text property is always applied.
In addition to global configuration properties, unblu also provides a number of other scopes for localized text properties. Scoped localized text properties are only applied in a certain context, i.e. for a specific user or for a specific domain.
In addition to java properties files, unblu also supports an xml based localized text file format. Certain localized text features (such as scope specific localized text, see above) are only supported in the xml based format.
The xml based format has the following general format.
A localized text file MUST NOT contain more than one domain section with the same "origin" attribute.
Example of a valid xml localized text file. Property key must be valid keys (see Unblu Server i18n Configuration) for real life files.