Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Date: Thu, 22 Sep 2016 18:22:21 +0000 (UTC)
From: "Scott Leschke (JIRA)" <jira@apache.org>
To: dev@felix.apache.org
Message-ID: <JIRA.13006914.1474568526000.640969.1474568541128@Atlassian.JIRA>
In-Reply-To: <JIRA.13006914.1474568526000@Atlassian.JIRA>
References: <JIRA.13006914.1474568526000@Atlassian.JIRA> <JIRA.13006914.1474568526123@arcas>
Subject: [jira] [Created] (FELIX-5357) cfg and jar file deletion
 inconsistency when  Karaf is offline
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 22 Sep 2016 18:22:23 -0000

Scott Leschke created FELIX-5357:
------------------------------------

             Summary: cfg and jar file deletion inconsistency when  Karaf is offline
                 Key: FELIX-5357
                 URL: https://issues.apache.org/jira/browse/FELIX-5357
             Project: Felix
          Issue Type: Bug
    Affects Versions: fileinstall-3.5.4
         Environment: Karaf 4.0.6.
            Reporter: Scott Leschke
            Priority: Minor


if a .cfg file is deleted while Karaf is running, the associated configuration record is deleted from Configuration Admin as well.  OTOH, if the file is deleted while Karaf is NOT running, the associated configuration record is retained when Karaf is started again. I would have expected that records for files that no longer exist would be deleted when configuration admin service starts.

Likewise, a similar behavior exists with .jar files. If a jar file is deleted while Karaf is running, the corresponding bundle is uninstalled. If the jar file is deleted while Karaf is offline, the corresponding bundle still exists in it's previous state when Karaf starts up again.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)