Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Date: Mon, 2 Sep 2013 15:50:51 +0000 (UTC)
From: "Carsten Ziegeler (JIRA)" <jira@apache.org>
To: dev@felix.apache.org
Message-ID: <JIRA.12666596.1378136949657.68538.1378137051576@arcas>
In-Reply-To: <JIRA.12666596.1378136949657@arcas>
References: <JIRA.12666596.1378136949657@arcas>
Subject: [jira] [Created] (FELIX-4214) Static cache in BundleResources is
 not updated
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Carsten Ziegeler created FELIX-4214:
---------------------------------------

             Summary: Static cache in BundleResources is not updated
                 Key: FELIX-4214
                 URL: https://issues.apache.org/jira/browse/FELIX-4214
             Project: Felix
          Issue Type: Bug
          Components: Metatype Service
    Affects Versions:  metatype-1.0.6
            Reporter: Carsten Ziegeler
            Priority: Critical
             Fix For: metatype-1.0.8


In some cases, the static cache in BundleResources is not updated correctly when a bundle is updated. It seems this is especially a problem, if there is more than one resource file for metatype information. In my case I experienced the problem with the following setup:
I'm using the scr plugin to generate the metatype information and this generates an xml for each metadata with a localization attribute set to the base of a custom properties file containing i18n translations, so something like localization=OSGI-INF/metatype/myservice
And I have a properties file at OSGI-INF/metatype/myservice.properties

In most cases, it seems this properties file is not found/read - however, after N updates of my bundle containing this, it starts to work and the properties file is picked up. Restarting the framework makes it fail again, until another couple of bundle updates.
If the default file OSGI-INF/metatype/metatype is specified in the localization field, this file (metatype.properties) is always picked up.

Disabling the static cache resourcesByBundle in BundleResources solves the problem

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira