THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Property | Default | Description |
|---|---|---|
| 2000 ms | Number of milliseconds between 2 polls of the directory |
| ./load | The name of the directory to watch |
| -1 | Debug information |
| true | Automatically start newly discovered bundles |
| A regular expression to be used to filter file names | |
| ./tmp | The name of the temporary directory to use with exploded or transformed bundles |
Once started, the values of these properties are printed to the console.
...
| Code Block | ||
|---|---|---|
| ||
felix.fileinstall.poll=2000
felix.fileinstall.dir=/configDir
felix.fileinstall.debug=-1
felix.fileinstall.filter=.*\\.cfg
felix.fileinstall.bundles.new.start=false
|
Exploded bundles
Apache Felix File Install has the ability to watch for exploded bundles and automatically update such bundles if the content is changed in any way. If a watched directory contains a sub directory, its content will be jar'ed and deployed to the OSGi framework. Any change to a file in this directory or one of its subdirectories will result in the directory to be jar'ed again and the corresponding bundle to be updated.
Custom artifacts
Apache Felix File Install can support deployment of custom artifacts. By default, configurations and plain OSGi bundles are supported, but other kind of artifacts can be deployed through custom artifact handlers.
To add support for a custom artifact, a service implementing one of org.apache.felix.fileinstall.ArtifactListener's sub interfaces must be registered in the OSGi registry.