JME Embedded Profile Platform

JME Embedded Profile requires CLDC-8 as underlying configuration.

General Guidelines for Application Behavior on Different Execution Environments

The JME Embedded Profile application model, including packaging, provisioning (if supported), lifecycle, and APIs, MUST be uniform regardless of the underlying execution environment. The essential aspects of the application model, such as application packaging (including the definition of JAD, JAR and manifest formats), provisioning semantics (if any), installation and removal, and the overall application lifecycle MUST remain constant.

Implementation independence. The behavior of APIs and functions MUST be independent of the implementation details of the underlying configuration or platform. The application specifies the execution environment that it requires. The specification of the execution environment is defined in the package documentation for javax.microedition.midlet.MIDlet.

Platform Default Character Encoding

The CLDC-8 specification defines the microedition.encoding system property, used to determine the character encoding to be used when none is explicitly specified in various input stream and string operations that depend on interpreting bytes as characters. This is known as the "platform default character encoding". The CLDC specification defines "UTF-8" (see [RFC2279]) as the default value.

For IMP_NG and IMP 1.0 applications (identified as such by the value of the MicroEdition-Profile attribute), when adapted to run in an JME Embedded Profile environment, the value of the microedition.encoding system property MUST continue to be whatever the implementation used earlier, as it varies between existing implementations. Accordingly, the APIs mentioned above MUST work as determined by the system property values. This guarantees backward compatibility for existing applications.