[
https://issues.apache.org/jira/browse/KARAF-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré reassigned KARAF-2441:
-------------------------------------------
Assignee: (was: 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
> Affects Versions: 3.0.0
> Environment: -
> Reporter: Robert Weiser
> Priority: Major
>
> 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 was sent by Atlassian Jira
(v8.3.4#803005)
