FileInstall: Property "felix.fileinstall.filter" ignored when the service start

When the fileinstall service start, it scan the container to find bundles already deployed whose location refers to a file in the configured folder.

However, this scan ignore the "felix.fileinstall.filter" : a bundle whose location is in the configured folder is registered by the DirectoryWatcher regardless of his name.

for instance, i have a Karaf instance with the following configuration :
folder: etc, filter: *.cfg, startLevel = 30
folder: etc, filter: *.xml, startLevel = 80

if i add a blueprint file in "etc", it will be transformed into a bundle at location "blueprint:file:etc/myfile.xml". Then, if i restart the container, this bundle will be registered by the two instances of DirectoryWatcher, and nasty things will happen (randomly refresh of this bundle, bundle not starting, etc)