I'm trying to use fileinstall and configadmin. What I'm finding is that
fileinstall STOPS processing .cfg files if there are extra .cfg in the scanned
directory. Here is what I'm doing:
1) In the properties that starts the Felix framework:
# Set up fileinstall to look for .cfg files in the conf directory
# to configure auto-started bundles.
felix.fileinstall.dir=conf
felix.fileinstall.debug=4
felix.fileinstall.filter=.*\\.cfg
felix.fileinstall.bundles.new.start=false
felix.fileinstall.noInitialDelay=true
2) The fileinstall (3.0.0) and configadmin (1.2.4) bundles are in my "bundle"
directory. They are auto-started.
3) In my "conf" directory I have the following
org.apache.felix.fileinstall-deploy.cfg
felix.fileinstall.dir=deploy
felix.fileinstall.debug=4
felix.fileinstall.noInitialDelay=true
4) I have a bundle in my "deploy" directory that registers a ManagedService
with a service.pid of "foo".
5) I have a file in my "conf" directory called "foo.cfg".
Up to this point, things work. All bundles in my "deploy" directory start and
my bundle receives an updated() call with the properties in foo.cfg.
Here's where things go wrong...
6) Add a file named "bar.cfg" to "conf" and restart.
Now, NONE of my "deploy" bundles are loaded at all. It seems that an arbitrary
.cfg file in the conf directory can bring things to a ginding halt. If I
remove the file and restart - everything works great.
Is this a known issue? I'm wondering if fileinstall/configadmin should be
handling this more gracefully.
Thanks,
rich
