Scribd
Upload
14 views

Java Learning

The J2ME architecture comprises three layers: the configuration layer containing the JVM, profile layer containing minimum APIs, and MIDP layer containing Java APIs for user interfaces, storage, and networking. Key configurations include CLDC for limited devices and CDC for more advanced devices. The MIDP profile is used with CLDC and provides classes for storage, UI, and networking for mobile devices, while other profiles like Foundation provide core classes or capabilities for games, PDAs, complex UIs, and more. A manifest file identifies a MIDlet suite's name, version, vendor, required profile and configuration, and lists the MIDlets in the suite.

Uploaded by

Roger S. Madhu
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
14 views

Java Learning

The J2ME architecture comprises three layers: the configuration layer containing the JVM, profile layer containing minimum APIs, and MIDP layer containing Java APIs for user interfaces, storage, and networking. Key configurations include CLDC for limited devices and CDC for more advanced devices. The MIDP profile is used with CLDC and provides classes for storage, UI, and networking for mobile devices, while other profiles like Foundation provide core classes or capabilities for games, PDAs, complex UIs, and more. A manifest file identifies a MIDlet suite's name, version, vendor, required profile and configuration, and lists the MIDlets in the suite.

Uploaded by

Roger S. Madhu
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

J2ME Configurations

Connected Limited Device Configuration (CLDC) Connected Device Configuration (CDC). Mobile Information Device Profile (MIDP) The Foundation Profile is used with the CDC configuration and is the core for nearly all other profiles used with the CDC configuration because the Foundation Profile contains core Java classes. The Game Profile is also used with the CDC configuration and contains the necessary classes for developing game applications for any small computing device that uses the CDC configuration. The Mobile Information Device Profile (MIDP) is used with the CLDC configuration and contains classes that provide local storage, a user interface, and networking capabilities to an application that runs on a mobile computing device such as Palm OS devices. MIDP is used with wireless Java applications. The PDAProfile (PDAP) is used with the CLDC configuration and contains classes that utilize sophisticated resources found on personal digital assistants. These features include better displays and larger memory than similar resources found on MIDP mobile devices (such as cell phones). The Personal Profile is used with the CDC configuration and the Foundation Profile and contains classes to implement a complex user interface. The Foundation Profile provides core classes, and the Personal Profiles provide classes to implement a sophisticated user interface, which is a user interface that is capable of displaying multiple windows at a time. The Personal Basis Profile is similar to the Personal Profile in that it is used with the CDC configuration and the Foundation Profile. However, the Personal Basis Profile provides classes to implement a simple user interface, which is a user interface that is capable of displaying one window at a time. The RMI Profile is used with the CDC configuration and the Foundation Profile to provide Remote Method Invocation classes to the core classes contained in the Foundation Profile.

The J2ME architecture comprises three software layers (Figure 3-1). The first layer is the configuration layer that includes the Java Virtual Machine (JVM), which directly interacts with the native operating system. The configuration layer also handles interactions between the profile and the JVM. The second layer is the profile layer, which

consists of the minimum set of application programming interfaces (APIs) for the small computing device. The third layer is the Mobile Information Device Profile (MIDP). The MIDP layer contains Java APIs for user network connections, persistence storage, and the user interface. It also has access to CLDC libraries and MIDP libraries.

Lets step through the manifest file shown in Listing 3-1. The MIDlet-Name attribute specifies the name of the MIDlet suite, which is Best MIDlet in this example. The MIDlet-Version and MIDlet-Vendor attributes identify the version number of the MIDlet suite and the company or person who provided the MIDlet suite. The MIDlet-n attribute contains information about each MIDlet that is in the JAR file. The number of the MIDlet replaces the letter n. In this example, the n is replaced with the digit 1 because there is only one MIDlet in the MIDlet suite. The MIDlet-n attribute can contain three values that describe the MIDlet. A comma separates each value. The first value is the name of the MIDlet, which is BestMIDlet.

Next is an optional value that specifies the icon that will be used with the MIDlet. In this example, BestMIDlet.png is the icon. The icon must be in the PNG image format. And the last value for the MIDlet-n attribute is the MIDlet class name, which is Best.BestMIDlet. The application manager uses the class name to load the MIDlet. The next MIDlet-n attribute is the MicroEdition-Profile whose value is the J2ME profile that is required to run the MIDlet. In this example the MIDP-1.0 profile is required. And the last MIDlet-n attribute is the MicroEdition-Configuration. The MicroEdition-Configuration attribute identifies the J2ME configuration that is necessary to run the MIDlet.

Page 42

You might also like