| Exit Print View | |
Java Platform Micro Edition Software Development Kit Version 3.0 |
|
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
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)
Having an emulator does not eliminate the need to test your application on actual target devices. An emulator can only approximate a device’s user interface, functionality, and performance. For example, an emulator may not accurately simulate processing speed, so an application may run faster or slower on a target device than it does on an emulator.
Java ME SDK simplifies deployment to and debugging on real devices running the Sun Java runtime. This version supports Windows Mobile platform based devices, and includes a bundled Java runtime for Windows Mobile devices.
The Microsoft Device Emulator is an example of third-party emulator integration. It means you can deploy applications to Microsoft Device Emulator as easily as you can run on our built-in emulators. See the following topics: CLDC Emulator Installation for a Device Running Windows Mobile and CLDC Installation for Windows Mobile.
|
