Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
DSDP/MTJ/Localize
Back to main DSDP-MTJ Use Cases
Short description:
Priority:
Owner:
Status:
- Proposed:|Accepted: date_here
- Identified|Described|Outlined|Detailed
Community Review: review_date_here
Use Case Specification: Localize
1. Use Case Description
ResourceBundle class is not available on CLDC configuration. To support String localization we provide MTJ class wizard that generates ResourceBundle like class that offers basic String localization functionalities to CLDC environment. Localization data is stored to properties files.
Properties files naming has special meaning to ResourceHandler class. The format is <basename>_<locale extension>. properties. Locale extension is a string that should match setLocale string ID. First ResourceHandler is searching resources from properties file where locale extension matches with entered locale ID. If there is no such properties file base properties are used.
Basic set of properties files that contain localized strings for base properties, Finnish and English locales:
- Messages.properties
- Messages_fi.properties
- Messages_en.properties
Generated ResourceHandler classes most important methods are
- Public static String getResource(“key”) // returns localized string
- Public static void setLocale(“fi”) // sets used locale
2. Basic Flow
- B1: The user chooses to use MTJ localization class wizard.
- B2: On wizard the user defines class name, package and base name.
- B3: ResourceHandler class is generated to projects src folder.
- B4: The user creates required property files and enters key value pairs to them.
- B5: The user replaces hard coded Strings with ResourceHandler.getResource(“key”) call.
3. Alternate Flows
Alternate_flow_name1:
- A1:
- A2:
- ...
Alternate_flow_name2:
- A1:
- A2:
- ...
4. Preconditions
4.1 MTJ Project is created
5. Postconditions
5.1 Project contains generated class
6. Extension Points
7. Special Requirements
8. Additional Information
Comments:
Back to main DSDP-MTJ Use Cases