Bundle Activator Wizard: Miscellaneous Options Page

This page of the wizard gathers further miscellaneous information from the user that is needed for generating an activator.

Miscellaneous Options

Custom start and stop: Select this checkbox if the bundle activator has behavior that must be performed exactly once when the bundle starts, and exactly once when the bundle stops, regardless of the availability of imported services. The hook methods start() and stop() will be generated.
Start asynchronously: Select this checkbox if the bundles activator must start asynchronously, on a private thread. The configuration parameter method isStartAsync() will be generated. The priority of the thread is controlled by the configuration parameter method getAsyncStartPriority(), which is generated based on the following selection relative to Thread.NORM_PRIORITY:
- Normal priority + 1: Select this radio button if the thread is to have a priority of Thread.NORM_PRIORITY + 1.
- Normal priority: Select this radio button if the thread is to have a priority of Thread.NORM_PRIORITY. Since this is the default priority, selecting this radio button does not cause the method getAsyncStartPriority() to be generated.
- Normal priority - 1: Select this radio button if the thread is to have a priority of Thread.NORM_PRIORITY - 1.
Load properties: Select this checkbox if the bundle should load a properties file. The query method getProperties() should be used to access the properties. The query method getPropertiesInputStream() will be generated based on the following:
- Properties filename: This field contains the name of the properties file. This field is automatically populated based on the bundle's Bundle-SymbolicName manifest header.
- From package resource: Select this radio button if the property file exists as a package resource. The properties file must reside in the same package as the bundle activator.
- From file system: Select this radio button if the property file exists in the local file system. The file must reside in the VM's current directory.
Has uninstall policy: Select this checkbox if the bundle should use one of SAT's uninstall policies. By default bundles are never automatically uninstalled. When using SAT a bundle developer can choose one of the following automatic uninstall policies:
- Uninstallable: Select this radio button if the bundle must be automatically uninstalled when its last dependent bundle is uninstalled. The configuration parameter method isUninstallable() will be generated. This behavior is useful to prevent an orphan bundle from remaining installed after its dependent bundles have been uninstalled.
- Transient: Select this radio button if the bundle must be automatically uninstalled once it has successfully started. The configuration parameter method isTransient() will be generated. This behavior is useful for a bundle that is designed to perform administration or diagnostic behavior that should execute only once. A bundles that uses this uninstall policy typically does not export any services.

| Next