You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2013/08/13 03:56:47 UTC

[jira] [Assigned] (KARAF-2441) Configuration Handling of deployed artifacts

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

Jean-Baptiste Onofré reassigned KARAF-2441:
-------------------------------------------

    Assignee: Jean-Baptiste Onofré
    
> Configuration Handling of deployed artifacts
> --------------------------------------------
>
>                 Key: KARAF-2441
>                 URL: https://issues.apache.org/jira/browse/KARAF-2441
>             Project: Karaf
>          Issue Type: New Feature
>          Components: karaf-config, karaf-feature, karaf-kar
>    Affects Versions: 3.0.0
>         Environment: -
>            Reporter: Robert Weiser
>            Assignee: Jean-Baptiste Onofré
>
> Bundling an application as a _.kar_ artifact containing the application-specific configuration yields the following problem if deploying it at the customer site:
> * deploying a _.kar_ will install all contained features including the configuration - this is not an "install" this will install + start all bundles part of the features
> Due to that the application will run with possibly wrong configuration if started for the first time - well one could of course create/deploy all configuration by hand (seems tedious though and IMHO goes against the concept of having a single artifact containing everything neccessary to run the application).
> The other problem is configuration management when updating the application - currently one can only replace configuration if defining a _configFile_ node in the _features.xml_ (it is not possible to add(/remove) single entries). Working with a _config_ node gives more control, however the configuration is not backed by a file thus not a usable approach to manage configuration for a customer running the OSGI application.
> ...in essence I was wondering about the intended configration management for real world applications. IMHO it should be possible to configure a .kar bundled OSGI application prior to launching it.

--
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