Introduction To J2ME, Albeski

Developing Java 2 ME Applications
Abelski eLearning
www.abelski.com
Introduction
J2SE, J2EE & J2ME
 Sun Microsystems groups its Java technologies into groups.
 The three most important groups are the following platforms:

Java 2 SE (J2SE) Java 2 Standard Edition Platform
Java 2 EE (J2EE) Java 2 Enterprise Edition Platform
Java 2 ME (J2ME) Java 2 Micro Edition Platform
 The various platforms aren't fully separated from each other.
 Each platform includes a JVM, libraries of classes &

development tools.
04/02/08 © Abelski eLearning 3

J2SE, J2EE & J2ME
J2EE J2SE J2ME

J2ME Configurations
 The Java 2 Micro Edition platform has two possible

configurations:
CLDC Connected Limited Device Configuration
CDC Connected Device Configuration
 These two configurations target two different categories of

products:
Low End Devices
High End Devices

J2ME Configurations
J2SE CDC CLDC

J2ME Profiles
 On top of the configuration we can expect a profile (one or

more) to be deployed.
 A J2ME profile addresses a specific need, and it typically

includes class libraries that are more specific than the
classes libraries the configuration includes.
 Currently, MIDP (Mobile Information Device Profile) is the

most popular profile.

J2ME Profiles
Personal RMI Profile

Profile
MIDP PDAP
Profile Profile
Foundation Profile
CLDC CDC
J2ME

J2ME (CLDC/MIDP)
 This course focuses on developing J2ME application for

mobile telephones with J2ME running environment CLDC
configuration and MIDP profile.
 The mobile telephones mass market includes mobile

telephones that support the J2ME(CLDC/MIDP) running
environment.

The KVM
 The KVM is a compact portable small JVM designed for

resource constrained devices.
 The J2ME (CLDC/MIDP) devices use the KVM.

J2ME (CLDC/MIDP) & J2SE
 J2ME(CLDC\MIDP) java.lang package is a subset of the
J2SE java.lang package.
 J2ME(CLDC\MIDP) doesn’t allow controlling the class loader.
 J2ME(CLDC\MIDP) doesn’t support object finalization.
 J2ME(CLDC\MIDP) doesn’t support reflection.

 J2ME(CLDC\MIDP) doesn’t support a mechanism (like the
JNI) that enables writing native methods.
 J2ME(CLDC\MIDP) multi threading mechanism is very

similar to the one that the J2SE has.
 J2ME(CLDC\MIDP) Math class is a subset.
 J2ME(CLDC\MIDP) has smaller version of the String and

the StringBuffer classes.

 J2ME(CLDC\MIDP) has smaller version of the System and
the Runtime classes.
 J2ME(CLDC\MIDP) java.util package includes only few of

the classes and interface that exist in the J2SE version.
 J2ME(CLDC\MIDP) java.io package include only few of the

classes and the interfaces that exist in the J2SE version.

Developing The First Midlet
 The J2ME application model is very similar to the one used
by Java applets and Java servlets.
 You need to declare a class that extends the Midlet class.
 That class must be public and it must include a constructor

without parameters.

import javax.microedition.midlet.*;
import javax.microedition.lcdui.*;
public class Hello extends MIDlet

{
private Display display;
private Form form;
public Hello()
{
form = new Form("Hello");
display = Display.getDisplay(this);
}
public void startApp()

{
display.setCurrent(form);
}
public void pauseApp() { }

public void destroyApp(boolean cond) { }
}

 Run the Wireless Toolkit.

 Create new project.
File -> New Project
 Fill in the details of the new project.

Project Name
The project name is the name of the project you choose for your new work.
MIDlet Class Name
The MIDlet class name is the name of the class you declared as one that
extends Midlet. When developing a J2ME application composed of several
classes, among those classes there must be a class that extends Midlet. That
would be the main class (similar to the Applet model).

 Press the “Create Project” button to create your project.
 The wizard pop up dialog window allows you to configure

the project you are about to develop.

 One of the outcomes for creating the new project is the
creation of folders hierarchy specifically for the new project.
 Each project has its own specific folder.
 All projects folders are kept within the “apps” folder.
 Each project folder includes the following sub folders:

bin ...this folder will include the JAR/JAD created files.
src ...this folder should include all project source code.
lib ...this folder should include all additional third party classes we add.
res ...this folder should include all additional resource files (images, sound etc.).

 Write your source code and save it within the “src” folder.
 Choose “Build” to compile & preverify your code.

 Choose “Project” -> “Package” -> Create Package” in order
to create the JAR/JAD files.

 You can now find the JAR/JAD files within the “bin” folder of
your project.
 You can install the JAR and the JAD files on your mobile
telephone.
 Alternatively, you can choose “Run” and run your code via
the wireless toolkit on one of its emulators.

The Java Application Manager (JAM)
 The MIDlet life cycle is controlled by the Java Application
Manager (JAM).
The JAM is a MIDlet management software that controls the process of
installing, running and removing the MIDlets.
 When the user chooses to run a MIDlet, it is the JAM that

creates an instance of the MIDlet class and runs methods
on it.
The sequence of method that will be invoked on the MIDlet subclass instance is
defined by the MIDlet life cycle. Like the servlets and the applets, the midlets
also have a well-defined set of states.

 The JAM calls various methods on the midlet to signify
changes from one state to another.
These methods include the following: startApp(), pauseApp(), destroyApp() and
the MIDlet subclass constructors as well.

© Zindell Technologies, Ltd. 04/02/08
Developing Java 2 ME Applications
Abelski eLearning
www.abelski.com
© Abelski eLearning 1
Introduction
J2SE, J2EE & J2ME
 Sun Microsystems groups its Java technologies into groups.
 The three most important groups are the following platforms:

Java 2 SE (J2SE) Java 2 Standard Edition Platform
Java 2 EE (J2EE) Java 2 Enterprise Edition Platform
Java 2 ME (J2ME) Java 2 Micro Edition Platform
 The various platforms aren't fully separated from each other.
 Each platform includes a JVM, libraries of classes &

development tools.
Browsing at http://java.sun.com/ you can find on the right a list

of all available Java technologies.
J2SE, J2EE & J2ME
J2EE J2SE J2ME
J2ME Configurations
 The Java 2 Micro Edition platform has two possible

configurations:
CLDC Connected Limited Device Configuration
CDC Connected Device Configuration
 These two configurations target two different categories of

products:
Low End Devices
High End Devices
These two configurations target two categories of products:

High-end devices (TV set-top boxes, Internet TVs, automobile
navigation systems etc�) which have large range of user
interface capabilities, high-bandwidth network connections
(usually TCP/IP) and more memory and CPU power.
and
Low-end devices (Cell phones, pagers, PDA�s etc�) which
have very simple user interface and small screen size, less
memory, less CPU power, lower bandwidth and most of them
are usually operated using batteries.
J2ME Configurations
J2SE CDC CLDC
J2ME Profiles
 On top of the configuration we can expect a profile (one or

more) to be deployed.
 A J2ME profile addresses a specific need, and it typically

includes class libraries that are more specific than the
classes libraries the configuration includes.
 Currently, MIDP (Mobile Information Device Profile) is the

most popular profile.
A J2ME configuration defines the Java language, the virtual

machine features and the minimum class libraries for a
category\group of devices (�horizontal� market).
A J2ME profile is layered on top of configuration and address
the specific demands of a specific vertical market (or device
category). The profile typically includes class libraries that are
far more specific than the class libraries provided in a
configuration.
J2ME Profiles
Personal RMI Profile

Profile
MIDP PDAP
Profile Profile
Foundation Profile
CLDC CDC
J2ME
J2ME (CLDC/MIDP)
 This course focuses on developing J2ME application for

mobile telephones with J2ME running environment CLDC
configuration and MIDP profile.
 The mobile telephones mass market includes mobile

telephones that support the J2ME(CLDC/MIDP) running
environment.
According to the specification, the MID profile has the following

characteristics:
At least 128KB of non-volatile memory (non-volatile memory is
memory that is capable of keeping its contents intact as the
device is turned on and off. The ROM is one example for non-
volatile memory) for the MIDP implementation.
At least 32KB of volatile memory for the heap.
At least 8KB of non-volatile memory for persistent data.
A screen of at least 96x54 pixels.
Pixel ratio approximately 1:1.
An Input mechanism � one of the following: keypad, keyboard
or touch screen.
Two-way network connection.
The classes a MIDP application can use come from packages
in both the CLDC and the MIDP. The packages the CLDC has
are: java.lang, java.io, java.util, javax.microedition.io. The
packages the MID profile adds are: javax.microedition.lcdui,
javax.microedition.midlet and javax.microedition.rms.
The KVM
 The KVM is a compact portable small JVM designed for

resource constrained devices.
 The J2ME (CLDC/MIDP) devices use the KVM.
According to the specification, the MID profile has the following

characteristics:
At least 128KB of non-volatile memory (non-volatile memory is
memory that is capable of keeping its contents intact as the
device is turned on and off. The ROM is one example for non-
volatile memory) for the MIDP implementation.
At least 32KB of volatile memory for the heap.
At least 8KB of non-volatile memory for persistent data.
A screen of at least 96x54 pixels.
Pixel ratio approximately 1:1.
An Input mechanism � one of the following: keypad, keyboard
or touch screen.
Two-way network connection.
The classes a MIDP application can use come from packages
in both the CLDC and the MIDP. The packages the CLDC has
are: java.lang, java.io, java.util, javax.microedition.io. The
packages the MID profile adds are: javax.microedition.lcdui,
javax.microedition.midlet and javax.microedition.rms.

 J2ME(CLDC\MIDP) java.lang package is a subset of the
J2SE java.lang package.
 J2ME(CLDC\MIDP) doesn’t allow controlling the class loader.
 J2ME(CLDC\MIDP) doesn’t support object finalization.
 J2ME(CLDC\MIDP) doesn’t support reflection.

 J2ME(CLDC\MIDP) doesn’t support a mechanism (like the
JNI) that enables writing native methods.
 J2ME(CLDC\MIDP) multi threading mechanism is very

similar to the one that the J2SE has.
 J2ME(CLDC\MIDP) Math class is a subset.
 J2ME(CLDC\MIDP) has smaller version of the String and

the StringBuffer classes.

 J2ME(CLDC\MIDP) has smaller version of the System and
the Runtime classes.
 J2ME(CLDC\MIDP) java.util package includes only few of

the classes and interface that exist in the J2SE version.
 J2ME(CLDC\MIDP) java.io package include only few of the

classes and the interfaces that exist in the J2SE version.

 The J2ME application model is very similar to the one used
by Java applets and Java servlets.
 You need to declare a class that extends the Midlet class.
 That class must be public and it must include a constructor

without parameters.

import javax.microedition.midlet.*;
import javax.microedition.lcdui.*;
public class Hello extends MIDlet

{
private Display display;
private Form form;
public Hello()
{
form = new Form("Hello");
display = Display.getDisplay(this);
}
public void startApp()

{
display.setCurrent(form);
}
public void pauseApp() { }

public void destroyApp(boolean cond) { }
}

 Run the Wireless Toolkit.

 Create new project.
File -> New Project
 Fill in the details of the new project.

Project Name
The project name is the name of the project you choose for your new work.
MIDlet Class Name
The MIDlet class name is the name of the class you declared as one that
extends Midlet. When developing a J2ME application composed of several
classes, among those classes there must be a class that extends Midlet. That
would be the main class (similar to the Applet model).

 Press the “Create Project” button to create your project.
 The wizard pop up dialog window allows you to configure

the project you are about to develop.
Press OK when the project configuration pop up window dialog

is shown. For now we will accept all default setting.

 One of the outcomes for creating the new project is the
creation of folders hierarchy specifically for the new project.
 Each project has its own specific folder.
 All projects folders are kept within the “apps” folder.
 Each project folder includes the following sub folders:

bin ...this folder will include the JAR/JAD created files.
src ...this folder should include all project source code.
lib ...this folder should include all additional third party classes we add.
res ...this folder should include all additional resource files (images, sound etc.).

 Write your source code and save it within the “src” folder.
 Choose “Build” to compile & preverify your code.
When developing a J2ME application there is a need to

preverify the source code (in addition to the compilation). The
KVM – unlike the JVM – is not capable of doing all code checks
before it runs it. Therefore, these checks are carried out via the
preverification stage.

 Choose “Project” -> “Package” -> Create Package” in order
to create the JAR/JAD files.

 You can now find the JAR/JAD files within the “bin” folder of
your project.
 You can install the JAR and the JAD files on your mobile
telephone.
 Alternatively, you can choose “Run” and run your code via
the wireless toolkit on one of its emulators.
Click to add title

● Click to add an outline
Click to add title

Click to add title


 The MIDlet life cycle is controlled by the Java Application
Manager (JAM).
The JAM is a MIDlet management software that controls the process of
installing, running and removing the MIDlets.
 When the user chooses to run a MIDlet, it is the JAM that

creates an instance of the MIDlet class and runs methods
on it.
The sequence of method that will be invoked on the MIDlet subclass instance is
defined by the MIDlet life cycle. Like the servlets and the applets, the midlets
also have a well-defined set of states.

 The JAM calls various methods on the midlet to signify
changes from one state to another.
These methods include the following: startApp(), pauseApp(), destroyApp() and
the MIDlet subclass constructors as well.

Introduction To J2ME, Albeski

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Introduction To J2ME, Albeski

Uploaded by

Copyright:

Available Formats

Developing Java 2 ME Applications

 Sun Microsystems groups its Java technologies into groups.

 The three most important groups are the following platforms:

 The various platforms aren't fully separated from each other.

 Each platform includes a JVM, libraries of classes &

04/02/08 © Abelski eLearning 3

J2EE J2SE J2ME

04/02/08 © Abelski eLearning 4

 The Java 2 Micro Edition platform has two possible

 These two configurations target two different categories of

04/02/08 © Abelski eLearning 5

J2SE CDC CLDC

04/02/08 © Abelski eLearning 6

 On top of the configuration we can expect a profile (one or

 A J2ME profile addresses a specific need, and it typically

 Currently, MIDP (Mobile Information Device Profile) is the

04/02/08 © Abelski eLearning 7

Personal RMI Profile

04/02/08 © Abelski eLearning 8

 This course focuses on developing J2ME application for

 The mobile telephones mass market includes mobile

04/02/08 © Abelski eLearning 9

 The KVM is a compact portable small JVM designed for

 The J2ME (CLDC/MIDP) devices use the KVM.

04/02/08 © Abelski eLearning 10

 J2ME(CLDC\MIDP) doesn’t allow controlling the class loader.

 J2ME(CLDC\MIDP) doesn’t support object finalization.

 J2ME(CLDC\MIDP) doesn’t support reflection.

04/02/08 © Abelski eLearning 11

 J2ME(CLDC\MIDP) multi threading mechanism is very

 J2ME(CLDC\MIDP) Math class is a subset.

 J2ME(CLDC\MIDP) has smaller version of the String and

04/02/08 © Abelski eLearning 12

 J2ME(CLDC\MIDP) java.util package includes only few of

 J2ME(CLDC\MIDP) java.io package include only few of the

04/02/08 © Abelski eLearning 13

 You need to declare a class that extends the Midlet class.

 That class must be public and it must include a constructor

04/02/08 © Abelski eLearning 14

public class Hello extends MIDlet

public void startApp()

public void pauseApp() { }

04/02/08 © Abelski eLearning 15

04/02/08 © Abelski eLearning 16

 Fill in the details of the new project.

04/02/08 © Abelski eLearning 19

 The wizard pop up dialog window allows you to configure

04/02/08 © Abelski eLearning 22

 Each project has its own specific folder.

 All projects folders are kept within the “apps” folder.

 Each project folder includes the following sub folders:

04/02/08 © Abelski eLearning 24

 Choose “Build” to compile & preverify your code.

04/02/08 © Abelski eLearning 26

04/02/08 © Abelski eLearning 28

04/02/08 © Abelski eLearning 30

 When the user chooses to run a MIDlet, it is the JAM that

04/02/08 © Abelski eLearning 34

04/02/08 © Abelski eLearning 35

Developing Java 2 ME Applications

04/02/08 © Abelski eLearning 1

04/02/08 © Abelski eLearning 2