felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From J. Brébec (JIRA) <j...@apache.org>
Subject [jira] [Updated] (FELIX-4661) FileInstall: Property "felix.fileinstall.filter" ignored when the service start
Date Wed, 01 Oct 2014 16:54:33 GMT

     [ https://issues.apache.org/jira/browse/FELIX-4661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

J. Brébec updated FELIX-4661:
    Attachment: fi.patch

Attached a patch fixing this issue

> FileInstall: Property "felix.fileinstall.filter" ignored when the service start
> -------------------------------------------------------------------------------
>                 Key: FELIX-4661
>                 URL: https://issues.apache.org/jira/browse/FELIX-4661
>             Project: Felix
>          Issue Type: Bug
>          Components: File Install
>    Affects Versions: fileinstall-3.4.2
>            Reporter: J. Brébec
>         Attachments: fi.patch
> 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)

This message was sent by Atlassian JIRA

View raw message