Alfresco 1.3 introduced a mechanism allowing you to include custom I18N strings. Previously webclient.properties would have to be changed and then re-merged when you upgraded.
A webclient.properties file can now be placed in the alfresco.extension package. This will be automatically picked up by the web client, except for messages displayed via JSF message tags directly in JSPs.
Using custom strings in JSPs
If you want to use a custom string in any of your JSPs then the options include:
The standard JSF mechanism can be used to load your custom bundle, for example add the following line to the top of your custom JSP page:
Note: In order to support dynamic web client properties the ResourceBundleWrapper will now order the resource bundles such that the repository extension (ie. /Company Home/Data Dictionary/Web Client Extension/webclient.properties) is searched first (if available) before the standard webclient.properties. This enables existing strings to be customised (for example, in a multi-tenant environment) in addition to adding new custom strings.
Using custom strings in configuration & beans
When we refer to I18N strings in configuration files or programtically via the Application.getMessage() call the standard webclient.properties and your custom webclient.properties (if present) are loaded.
For example, if you have a custom string with a key of custom_string, you could use it as the label for a property as follows: