Exit Print View

Java Platform Micro Edition Software Development Kit Version 3.0

Get PDF Book Print View

Document Information

Getting Started

Java ME Platform SDK Features

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

Monitoring Network Traffic

Lightweight UI Toolkit

Security and MIDlet Signing

BD-J Support

CLDC Emulation on a Windows Mobile Device

Installing CLDC Emulation on a Windows Mobile Emulator

On-device Debugging

Command Line Reference

Launching the SDK

Running the Device Manager

Managing Device Addresses (device-address)

Running the Emulator From the Command Line

MIDlet Options

CDC Options

Debugging and Tracing Options

Building a Project from the Command Line

Checking Prerequisites

Compiling Class Files

Preverifying Class Files

Packaging a MIDLet Suite (JAR and JAD)

Command Line Security Features

Changing the Emulator's Default Protection Domain

Signing MIDlet Suites (jadtool.exe)

Managing Certificates (MEKeyTool)

Generating Stubs (wscompile)

Running the Payment Console From the Command Line

Virtual Machine Memory Profiler (Java Heap Memory Observe Tool)

Running the Java Heap Memory Observe Tool

Viewing the Heap Snapshot

Running WMA Tool








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

JSRs 184, 226, and 239: Graphics Capabilities

JSR 205: Wireless Messaging API (WMA) Support

JSR 211: Content Handler API (CHAPI)

JSR 238: Mobile Internationalization API (MIA)

JSR 229: Payment API Support

JSR 256: Mobile Sensor API Support


Preverifying 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   -classpath ..\..\lib\cldcapi10.jar;..\..\lib\midpapi20.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.