The MicroEJ launch configuration sets up the MicroEJ Applications environment (main class, resources, target platform, and platform-specific options), and then launches a MicroEJ launch script for execution.
Execution is done on either the MicroEJ Platform or the MicroEJ Simulator. The launch operation is platform-specific. It may depend on external tools that the platform requires (such as target memory programming). Refer to the platform-specific documentation for more information about available launch settings.
The Main tab allows you to set in order:
- The main project of the application.
- The main class of the application containing the main method.
- Types required in your application that are not statically embedded from the main class entry point. Most required types are those that may be loaded dynamically by the application, using the Class.forName() method.
- Binary resources that need to be embedded by the application. These are usually loaded by the application using the Class.getResourceAsStream() method.
- Immutable objects’ description files. See the [BON 1.2] ESR documentation for use of immutable objects.
The next tab is the Execution tab. Here the target needs to be selected. Choose between execution on a MicroEJ Platform or on a MicroEJ Simulator. Each of them may provide multiple launch settings. This page also allows you to keep generated, intermediate files and to print verbose options (advanced debug purpose options).
The next tab is the Configuration tab. This tab shows the available Application options.
The next tab is the JRE tab. This tab allows you to configure the
Java Runtime Environment used for running the underlying launch script.
It does not configure the MicroEJ Application execution. The
VM Arguments text field allows you to set vm-specific options, which
are typically used to increase memory spaces:
To modify heap space to 1024MB, set the
To modify string space (also called PermGen space) to 256MB, set the
To set thread stack space to 512MB, set the
To set an advanced Application option, declare a system property with the following pattern
The next tab is the Source tab. By default, it is automatically configured to connect your Add-On Libraries sources dependencies. To connect your Platform Foundation Library sources, please refer to the section Foundation Library Sources.