DSDP/MTJ/JSR 238

Back to main DSDP-MTJ Use Cases

Short description:

Priority:

Owner:

Status: Proposed, Outlined

Proposed:|Accepted: date_here

Identified|Described|Outlined|Detailed

Community Review: review_date_here

---

Use-Case Specification: JSR238

1. Use Case Description

JSR238 provides API that offers solution to localization issues on CLDC environment. JSR238 declares binary format and folder structure for localization data on limited environment.

When API is present MTJ offers JSR238 editor that can transform localization data to human readable format and back to binary format. MTJ project contains information whether this option is enabled.

2. Basic Flow

B1: The user chooses to use MTJ JSR238 format in projects localization.

B2: The user gets to use JSR238 editor that can be used to manage localization data.

B3: The user applies data changes.

B4: Data is packed in JSR238 format on projects work area.

B5: The user builds application and localization “.res” files are packed to produced JAR file.

3. Alternate Flows

Importing localization data from JAR file

A1: The user defines JAR file that contains JSR238 data.

A2: Localization data is imported to MTJ projects workspace.

4. Preconditions

4.1 MTJ Project is created.

4.2 Used SDK contains JSR238 API.

5. Postconditions

5.1 Project contains generated resource files.

5.2 Build project JAR file contains resource files in correct folder structure.

5.3 Midlet using JSR238 API can retrieve packed data.

6. Extension Points

7. Special Requirements

8. Additional Information

---

Comments:

Back to main DSDP-MTJ Use Cases