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 2015/03/17 08:03:39 UTC

[jira] [Closed] (FELIX-2663) Allow ConfigInstaller to perform placeholder substitution from framework properties

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

Carsten Ziegeler closed FELIX-2663.
-----------------------------------

> Allow ConfigInstaller to perform placeholder substitution from framework properties
> -----------------------------------------------------------------------------------
>
>                 Key: FELIX-2663
>                 URL: https://issues.apache.org/jira/browse/FELIX-2663
>             Project: Felix
>          Issue Type: Improvement
>          Components: File Install
>    Affects Versions: fileinstall-3.0.2
>            Reporter: David Hay
>            Assignee: Guillaume Nodet
>             Fix For: fileinstall-3.1.0
>
>         Attachments: felix-fileinstall-context-properties.patch
>
>
> The ConfigInstaller class will perform placeholder substitution using configuration values defined elsewhere in the .cfg file or using System properties.  Would be nice if it could also use properties defined by the framework (i.e. BundleContext.getProperty())
> The use case is this:  As part of the OSGi framework initialization, some properties are set on the framework that define things such as a "home" directory.  The various configuration files could then refer to resources relative to this "home" directory.  For example:
> props.setProperty("app.home", homeDir); // homeDir provided by JNDI config, env variable, etc.
> frameworkFactory.newFramework(props);
> ...
> Then, in a configuration file read by the FileInstall bundle, it would be nice to be able to do:
> data.directory=${app.home}/data/



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