Where <cache-path> is the path you want to use as the bundle cache. If you specify a relative cache path, then it will be treated as relative to the current working directory.

-**Useful Information** -Previous versions of the framework prompted for a profile name when executed. The profile name was used to create a directory inside `.felix/` in the user home directory. This approach allowed users to have different sets of bundles for different purposes, e.g., testing, production, etc. If this behavior is still desired, it is very easy to mimic. Modify `conf/config.properties` to include "`felix.cache.rootdir=$\{user.home}/.felix`". Now, if you start Felix with something like "`java -jar bin/felix.jar foo`", it will use "`$\{user.home}/.felix/foo/`" as the bundle cache directory, where "`$\{user.home\`}" is automatically substituted with the appropriate system property by the launcher. +Useful Information
+Previous versions of the framework prompted for a profile name when executed. The profile name +was used to create a directory inside .felix/ in the user home directory. This +approach allowed users to have different sets of bundles for different purposes, e.g., testing, +production, etc. If this behavior is still desired, it is very easy to mimic. Modify +conf/config.properties to include "felix.cache.rootdir=${user.home}/.felix". +Now, if you start Felix with something like "java -jar bin/felix.jar foo", it will use +"${user.home}/.felix/foo/" as the bundle cache directory, where +"${user.home}" is automatically substituted with the appropriate system property by +the launcher.

Framework Shell

The main way to interact with the framework is via the supplied Apache Felix Gogo shell. After starting the framework, type help into the shell to see the list of the available commands and help <command-name> to get help for a specific command.

-**Useful Information** -In Gogo, command names are made up of two parts: `:`. This is similar to a fully qualified class name in Java and is used to avoid naming collisions. If the `` portion of the command is unique, then you only need to type it. If not, then you must either type the full `:` or arrange the scope search path accordingly. +Useful Information
+In Gogo, command names are made up of two parts: <scope>:<name>. This is similar +to a fully qualified class name in Java and is used to avoid naming collisions. If the +<name> portion of the command is unique, then you only need to type it. If not, +then you must either type the full <scope>:<name> or arrange the scope search path accordingly.

To install bundles, use the felix:install command, which is described in more detail in the next sub-section. To list installed bundles, use the felix:lb command. To stop the framework type stop 0 to stop the System Bundle; any installed bundles will automatically be reloaded (and potentially restarted) the next time you launch with the associated cache.

The felix:stop command is used to stop a bundle and the felix:uninstall command is used to remove a bundle from the bundle cache. As an alternative to using the felix:install and felix:start commands explicitly, it is also possible to install and start a bundle in one step by using the felix:start command with a bundle URL.

Bundles can be updated using the felix:update command. The update command allows you to specify an URL from which to retrieve the updated bundle, but if one is not specified it will try to update the bundle from the bundle's Bundle-UpdateLocation manifest attribute, if present, or the bundle's original location URL.

-**Useful Information** -When you use `felix:update` or `felix:uninstall`, the changes appear to take effect immediately, but in reality the changes are only partially enacted. If a bundle is updated or uninstalled and it was exporting packages, these packages are not removed until the framework is refreshed using the `PackageAdmin` service. The Felix shell offers a convenient `refresh` command for this purpose. This is the correct behavior as defined by the OSGi specification. +Useful Information
+When you use felix:update or felix:uninstall, the changes appear to take +effect immediately, but in reality the changes are only partially enacted. If a bundle is updated +or uninstalled and it was exporting packages, these packages are not removed until the framework +is refreshed using the PackageAdmin service. The Felix shell offers a convenient +refresh command for this purpose. This is the correct behavior as defined by the OSGi +specification.

For an introduction to writing bundles and services, refer to the Felix bundle tutorial.

Feedback

Subscribe to the Felix users mailing list by sending a message to users-subscribe@felix.apache.org; after subscribing, email questions or feedback to [users@felix.apache.org|mailto:users@felix.apache.org].

Apache Felix Framework Usage Documentation

Apache Felix Framework Usage Documentation

Downloading the Framework

Framework Shell

Feedback