Midlet Launching

When Midlet launching is specified, the emulator is instructed to execute the midlet from the local file system. Using this method of launching, it is not necessary to package the MIDlet prior to debugging.

When you select this option, you must provide the name of your MIDlet class.

JAD URL

When JAD URL is specified, the emulator loads the specified Java ME Application Descriptor specified in the text field. The specified JAD and the associated JAR file must be valid for launching. There is no build or packaging done when this option is selected.

Over The Air

When Over the Air is specified, the Eclipse emulator's Java Application Manager (JAM) will be instructed to contact EclipseME's built in HTTP server to download the suite. Starting with version 0.5.5, the Over the Air Preferences default to automatically deploying the project prior to launch. If you have disabled this feature, you will need to manually deploy the project prior to using this mode.

Project Device

The Device settings allow you to choose the device definition under which your MIDlet will be emulated. This is useful, for example, if you have written the MIDlet using one device, and then want to test it for compatibility under another.

By default, the MIDlet will be run under the device defined in the project properties. To change to a different platform, select the second radio button and choose the device from the selection controls.

Specific Device

This setting allows you to choose the specific device within the configuration under which your MIDlet will be emulated.

Security Domain

This pull-down list allows you to launch the emulator with a particular security domain selected. This can be useful to debug a signed MIDlet. For more information, see About MIDlet Suite Signing.

Extra Emulation Parameters

You have the option of adding extra parameters that will be passed directly to the emulator. This is useful if, for example, you want to enable tracing in the target JVM/KVM.