Run/Debug Configuration: J2ME
J2ME run/debug configuration options vary depending on the SDK you are using to develop your mobile applications. This section describes the options that are specific for WTK and DoJa, as well as the general options that apply to both SDKs.
In this text box, specify the name of the current run/debug configuration.
Select, which of the following sources - Jad, MIDlet class or OTA - is used to be run/debugged. Each source has its own settings described below.
If you have selected to use Jad file as the source for running and debugging, you need only to specify its location in the Jad File.
|If you have selected to use MIDlet class as the source for running and debugging, specify the following options: |
| These options can be set, if you have selected to use OTA as the source for running and debugging. This functionality emulates wireless download of the software from the server. Therefore, it is necessary to have a working server with such service and the necessary suite (which you want to install and launch) on it. This service is completely dependent on the emulator vendor and IntelliJ IDEA does not provide it. So, it should be provided by the emulator or separately by the emulator vendor (for instance, like Nokia does). Thus, you need to have three items ready - a server, a service and tested suite on that server. Remember that the actual options list varies from emulator type. |
Select which of the files, Jam or IApplication Class, is to be run/debugged.
If you have selected to use Jam file as the source for running and debugging, you need only to specify its location in the Jam File field.
If you want to use IApplication Class as source for running/debugging, specify its location in the IApplication Class field.
Select one of the available devices for the current emulator.
Opens the emulator's Preferences dialog. For more information, refer to emulator's documentation.
Opens the emulator's Utilities dialog. For more information, refer to emulator's documentation.
Type in/edit emulator parameters such as
Use classpath and JDK of module
Select a mobile module from the list of modules configured in your project. The classpath and JDK of this module will be used to run your J2ME module with the current run configuration.
When you edit a run configuration (but not a run configuration template), you can specify the following options for it:
In this text box, specify the name for the run/debug configuration. The name will help you identify the created configuration when you choose to edit it later, or when you invoke it, for example, from the Run popup (Shift+Alt+F10).
Select this checkbox to make the run/debug configuration available to other team members.
If the directory-based project format is used, the settings for a run/debug configuration are stored in a separate .xml file in the
If the file-based format is used, the settings are stored in the
Allow running in parallel
When disabled, every time a new run/debug configuration is launched, IntelliJ IDEA checks the presence of the other instances of the same run/debug configuration, and displays a confirmation dialog box. If you click OK in the confirmation dialog box, the first instance of the runner will be stopped, and the next one will take its place.
This makes sense when the usage of certain resources can cause conflicts, or when launching two run/debug configurations of the same type consumes too much of the CPU and memory resources.
If this checkbox is selected, it is possible to launch as many instances of the run/debug configuration as required. So doing, each runner will start in its own tab of the Run Tool Window or Debug Tool Window.
The tree view of run/debug configurations has a toolbar that helps you manage configurations available in your project as well as adjust default configurations templates.
Create a run/debug configuration.
Delete the selected run/debug configuration. Note that you cannot delete default configurations.
Create a copy of the selected run/debug configuration. Note that you create copies of default configurations.
View and edit the default template for the selected run/debug configuration. The templates are used for newly created configurations.
Move the selected run/debug configuration up and down in the list.
The order of configurations in the list defines the order, in which the configurations appear when you choose a run/debug configuration.
Default templates of run/debug configurations are always sorted alphabetically.
Move into new folder / Create new folder
You can group run/debug configurations by placing them into folders.
To create a folder, select the configurations within a category, click , and specify the folder name. If only a category is in focus, an empty folder is created.
Then, to move a configuration into a folder, between the folders or out of a folder, use drag-and-drop or and buttons.
To remove grouping, select a folder and click .
Click this button to sort configurations in the alphabetical order.
Under the Templates node in the tree view of run configurations, you can select a run configuration template and edit its default settings. This will not affect the configurations that are already created, but will be used as defaults when creating new configurations of the corresponding type.
When you select the Templates node itself, you will be able to adjust general settings that apply to all run/debug configurations:
Configurations available in Run Dashboard
In this section you can create a list of run configurations available in the Run Dashboard — a tool window that helps you execute and manage multiple run/debug configurations.
Note that the dashboard will only display the configuration types for which you have created one ore more configurations.
Thus, if you add a configuration type for which no configurations exist in the project, this type will not be displayed on the dashboard until you create a configuration of this type.
Confirm rerun with process termination
|The behavior of this checkbox depends on whether the Single instance only option is selected for a particular run/debug configuration. |
Temporary configurations limit
Specify the maximum number of temporary configurations to be stored and shown in the Select Run/Debug Configuration drop-down list.
Before Launch options
In this area you can specify tasks that must be be performed before starting the selected run/debug configuration. The tasks are performed in the order they appear in the list.
Click this icon to add one of the following available tasks:
Click this icon to remove the selected task from the list.
Click this icon to edit the selected task. Make the necessary changes in the dialog that opens.
Click these icons to move the selected task one line up or down in the list. (The tasks are performed in the order that they appear in the list.)
Show this page
Select this checkbox to show the run/debug configuration settings prior to actually starting the run/debug configuration.
Activate tool window
Otherwise, the tool window isn't shown. However, when the configuration is running, you can open the corresponding tool window for it yourself by pressing Alt+4 or Alt+5.