| Exit Print View | |
Java Platform Micro Edition Software Development Kit Version 3.0 |
|
Viewing and Editing Project Properties
Running Projects in the Emulator
Searching the WURFL Device Database
Finding Files in the Multiple User Environment
CLDC Emulation on a Windows Mobile Device
Installing CLDC Emulation on a Windows Mobile Emulator
Managing Device Addresses (device-address)
Running the Emulator From the Command Line
Building a Project from the Command Line
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)
Running the Payment Console From the Command Line
Virtual Machine Memory Profiler (Java Heap Memory Observe Tool)
Running the Java Heap Memory Observe Tool
JSR 82: Bluetooth and OBEX Support
JSR 135: Mobile Media API Support
JSR 177: Smart Card Security (SATSA)
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)
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 | directoriesSome of the options are as follows:
|
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 tmpclassesAs 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.
|
