You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2013/09/02 18:24:52 UTC
[jira] [Resolved] (FELIX-4214) Cache in BundleResources works only
for a single metatype properties file per bundle
[ https://issues.apache.org/jira/browse/FELIX-4214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler resolved FELIX-4214.
-------------------------------------
Resolution: Fixed
Solved by adding the basename to the cache key
> Cache in BundleResources works only for a single metatype properties file per bundle
> ------------------------------------------------------------------------------------
>
> 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
> Assignee: 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