Page History

...

Note that the framework does not use system properties to find its configuration properties, it only consults the map passed into its constructor. In contrast to bundles, which use BundleContext.getProperty(), which exposes both configuration and system properties at execution time. In the case of overlap, the configuration properties override system properties. As a convenience, if you are using the Felix launcher, it will copy all configuration properties it finds in the system properties to the configuration map passed into the framework constructor, which allows you to set configuration properties on the command line. This feature is not available if you are just using the Felix framework JAR file.

The following configuration properties are for the launcher:

...

Framework configuration properties

...

The following configuration properties are for the framework (properties starting with "felix" are specific to Felix, while those starting with "org.osgi" are standard OSGi properties):

...

The Felix framework distribution contains a default conf/config.properties.

Anchor
laucher laucher

Launcher configuration properties

The following configuration properties are for the launcher:

• felix.auto.deploy.dir - Specifies the auto-deploy directory from which bundles are automatically deploy at framework startup. The default is the bundle/ directory of the current directory.
• felix.auto.deploy.action - Specifies a comma-delimited list of actions to be performed on bundle JAR files found in the auto-deploy directory. The possible actions are install, update, start, and uninstall. An undefined or blank value is equivalent to disabling auto-deploy processing.
• felix.auto.install.<n> - Space-delimited list of bundle URLs to automatically install when Felix is started, where <n> is the start level into which the bundle will be installed (e.g., felix.auto.install.2).
• felix.auto.start.<n> - Space-delimited list of bundle URLs to automatically install and start when Felix is started, where <n> is the start level into which the bundle will be installed (e.g., felix.auto.start.2).
• felix.shutdown.hook - Specifies whether the launcher should install a shutdown hook to cleanly shutdown the framework on process exit. The default value is true.

Migrating from Earlier Versions

Apache Felix Framework 2.0.0 introduced some configuration property changes. This section describes the differences from older versions of the framework.

...