Exit Print View

Java Platform Micro Edition Software Development Kit Version 3.0, Mac OS

Get PDF Book Print View

Document Information

Getting Started


Using Sample Projects

Creating and Editing Projects

Viewing and Editing Project Properties

Running Projects in the Emulator

Searching the WURFL Device Database

Finding Files in the Multiple User Environment

Profiling Applications

Network Monitoring

Lightweight UI Toolkit

Security and MIDlet Signing

CLDC Emulation on a Windows Mobile Device

Installing CLDC Emulation on a Windows Mobile Emulator (Windows Only)

On-device Debugging

Command Line Reference

Launch the SDK

Run the Device Manager

Manage Device Addresses (device-address)

Emulator Command Line Options

Build a Project from the Command Line

Packaging a MIDLet Suite (JAR and JAD)

Command Line Security Features

Change the Default Protection Domain

Sign MIDlet Suites (jadtool)

Manage Certificates (MEKeyTool)

Generate Stubs (wscompile)

Virtual Machine Memory Profiler (Java Heap Memory Observe Tool)

Run the Java Heap Memory Observe Tool

Heap Snapshot Elements


JSR Support

JSR 75: PDA Optional Packages

JSR 82: Bluetooth and OBEX Support

JSR 135: Mobile Media API Support

JSR 172: Web Services Support

JSR 177: Smart Card Security (SATSA)

JSR 179: Location API Support

JSR 180: SIP Communications

JSR 184: Mobile 3D Graphics

JSR 205: Wireless Messaging API (WMA) Support

JSR 211: Content Handler API (CHAPI)

JSR 226: Scalable 2D Vector Graphics

JSR 229: Payment API Support

JSR 238: Mobile Internationalization API (MIA)

JSR 256: Mobile Sensor API Support


Build a Project from the Command Line

In the user interface, building a project is a single step. Behind the scenes, however, there are two steps. First, Java source files are compiled into Java class files. Next, the class files are preverified, which means they are prepared for the CLDC VM. See the following topics:

Check Prerequisites

Before building and running an application from the command line, verify that you have a version no earlier than 1.5 of the Java SE software development kit. Make sure the jar command is in your path. To find the version of the development kit, run java -version at the command line.

Compile Class Files

Use the javac compiler from the Java SE development kit to compile Java source files. You can use the existing Java ME Platform SDK project directory structure. Use the -bootclasspath option to tell the compiler to use the MIDP APIs, and use the -d option to tell the compiler where to put the compiled class files.

The following example demonstrates how you might compile a MIDP 2.0 application, taking source files from the src directory and placing the class files in the tmpclasses directory. Newlines have been added for clarity.

javac -target 1.3 -source 1.3 
   -bootclasspath ../../lib/cldc_10.jar;../../lib/midp2.0.jar
   -d tmpclasses

For more information on javac, consult the Java SE documentation.

Preverify Class Files

The next step is to preverify the class files. The bin directory of the Java ME Platform SDK includes the preverify utility. The syntax for the preverify command is as follows:

preverify files | directories

Some of the options are as follows:

-classpath classpath
Specify the directories or JAR files (given as a semicolon-delimited list) from which classes are loaded.
-d output-directory
Specify the target directory for the output classes. This directory must exist before preverifying. If this option is not used, the preverifier places the classes in a directory called output.

Following the example for compiling, use the following command to verify the compiled class files. As before, newlines are added for clarity.


preverify.exe   -classpath ..\..\lib\cldcapi10.jar;..\..\lib\midpapi20.jar   -d classes   tmpclasses

Mac OS and Linux

preverify   -classpath ../../lib/cldc_10.jar;../../lib/midp2.0.jar   -d classes   tmpclasses

As a result of this command, preverified class files are placed in the classes directory. If your application uses WMA, MMAPI, or other versions of CLDC or MIDP, be sure to include the relevant .jar files in the classpath.