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 (Windows Only)
JSR 82: Bluetooth and OBEX Support
JSR 135: Mobile Media API Support
JSR 177: Smart Card Security (SATSA)
JSR 205: Wireless Messaging API (WMA) Support
JSR 211: Content Handler API (CHAPI)
JSR 226: Scalable 2D Vector Graphics
JSR 238: Mobile Internationalization API (MIA)
JSR 256: Mobile Sensor API Support
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 devices, and includes a bundled Java runtime for Windows Mobile devices.
On Windows, 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 the SDK’s built-in emulators. This promotes consistent behavior between applications running on the Microsoft Device emulator and applications running on a device running Windows mobile. See the topics CLDC Emulator Installation for a Device Running Windows Mobile and CLDC Installation for Windows Mobile.
On Mac OS there is no integration with the Microsoft Device Emulator, but you can install and debug applications on a real device. See CLDC Emulator Installation for a Device Running Windows Mobile, Adding Devices With the Device Wizard (Mac OS), and Wireless Debugging Procedure.