felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Valentin Valchev (JIRA)" <j...@apache.org>
Subject [jira] Updated: (FELIX-2668) Add localization for the meta-type
Date Mon, 25 Oct 2010 12:57:20 GMT

     [ https://issues.apache.org/jira/browse/FELIX-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Valentin Valchev updated FELIX-2668:

    Attachment: meta-data-localization.patch

Here is the patch. It includes the English and Bulgarian localization.

> Add localization for the meta-type
> ----------------------------------
>                 Key: FELIX-2668
>                 URL: https://issues.apache.org/jira/browse/FELIX-2668
>             Project: Felix
>          Issue Type: Improvement
>          Components: Web Console
>    Affects Versions: webconsole-3.1.2
>            Reporter: Valentin Valchev
>         Attachments: meta-data-localization.patch
> Currently the meta-type provider ConfigurationListener2 uses hard-coded values for description
of the properties. So as example, when you switch to German language and go to the Configuration,
you will see the English metatype information for the web console configuration.
> What about having a resource file containing the meta-type data? A separate or event
the same i18n properties, that we use for localizing the UI!
> So in implementation of getObjectClassDefinition( String id, String locale ), we can
use the locale parameter and get the correct resource bundle.
> The we can assume the localization keys for the Object Class Definition are:
> metadata.name=Apache Felix OSGi Management Console
> metadata.description=Configuration of the Apache Felix OSGi Management Console.
> and for each attribute it can be:
> metadata.<key>.name=the name
> metadata.<key>.description=description
> or as example for 'manager.root' property it will be:
> metadata.manager.root.name=Root URI
> metadata.manager.root.description=The root path to the OSGi Management Console

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message