| Exit Print View | |
Java Platform Micro Edition Software Development Kit Version 3.0 |
|
|
Java ME Platform SDK Features > Adding a Java Platform > Choose Custom Java ME MIDP Platform Emulator |
|
J2ME Platforms (CLDC and MIDP)
Choose Platform Folder and Name (Java SE and CDC)
Choose Location (JavaSE and CDC)
Create a Platform for Legacy CDC Projects
Choose Java ME MIDP Platform Folders
Choose Custom Java ME MIDP Platform Emulator
Support for Third-Party Emulators and Real Devices
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
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)
This wizard page defines the general parameters for an emulator that is not UEI compliant. You must supply this information:
Platform Home. The path to the directory where the emulator platform is installed. You can enter a path, or use the Browse button to navigate to the directory.
Platform Name. A name for the emulator platform.
Device Name. A name for the specific device the platform emulates.
Preverify Command. The command line syntax that invokes the preverify application to preverify a MIDlet. MIDlet class files must be preverified before they can be run on a device or emulator. The toolkit silently handles preverification during the build process. See the CLDC specification for more information on preverification.
Execution Command. The command line syntax that invokes the emulator to execute a MIDlet.
Debugger Command. The command line syntax that invokes the emulator to debug a MIDlet.
To see descriptions of the command line syntax parameters, click in the appropriate field. The description is displayed in the area below the debugger command. Click Next when you are finished.
|
|