| Exit Print View | |
Java Platform Micro Edition Software Development Kit Version 3.0, CLDC |
|
|
|
Configuring the Web Browser and Proxy Settings
Running MIDP and CLDC Sample Projects
Running the Demos Sample Project
Viewing and Editing Project Properties
Running Projects in the Emulator
Searching the WURFL Device Database
Finding Files in the Multiple User Environment
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
Sometimes even a “known good“ application, such as a sample project, does not run successfully. The problem is usually your environment.
Some demonstrations require specific setup and instructions. For example, if a sample uses web services and you are behind a firewall, you must configure the emulator’s proxy server settings or web access will fail. See Configuring the Web Browser and Proxy Settings.
If an application must run over the air (OTA), the SDK automatically installs it in the device instance.
To perform the installation, MIDlet Suites use sdk-installdir/runtimes/cldc-hi-javafx/bin/runMidlet.
Mac:
installdir/Contents/Resources/runtimes/cldc-hi-javafx/bin/runMidlet
installdir/runtimes/cdc-hi/bin/cvm
Because these programs are launched remotely, virus checking software can prevent them from running. If this happens, the project compiles, but the emulator never opens. In the console you see warnings that the emulator cannot connect.
Consider configuring your antivirus software to exclude runMidlet.
See also Troubleshooting.
|
|