[KARAF-2441] Configuration Handling of deployed artifacts

• Type: New Feature
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.0.0
• Component/s: karaf

Environment

-

• Assignee: Unassigned
• Reporter: Robert Weiser
• Created: 12/Aug/13 08:55
• Updated: 09/Oct/20 04:07

Description

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.