karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Schneider (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-4565) Set ConfigurationPolicy.REQUIRE for decanter appenders and collectors
Date Thu, 09 Jun 2016 07:49:21 GMT

    [ https://issues.apache.org/jira/browse/KARAF-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15322101#comment-15322101

Christian Schneider commented on KARAF-4565:

It came up with the spring boot support but it is relevant for all deployments where you can
not change the running bundles at runtime.

As long as we deploy the default configs using the features the behaviour in plain karaf should
be the same.

> Set ConfigurationPolicy.REQUIRE for decanter appenders and collectors
> ---------------------------------------------------------------------
>                 Key: KARAF-4565
>                 URL: https://issues.apache.org/jira/browse/KARAF-4565
>             Project: Karaf
>          Issue Type: Improvement
>          Components: decanter
>    Affects Versions: decanter-1.1.0
>            Reporter: Christian Schneider
>            Assignee: Christian Schneider
>             Fix For: decanter-1.1.1
> Currently decanter components start with defaults if no config is supplied.
> I would like to change this so the component only starts if a config is supplied. Defaults
still apply but the presence of an empty  config can then be used to swtich the component
on and off.
> This is especially important for fixed deployments were a set of components is deployed
but you want to configure which ones to actually use.

This message was sent by Atlassian JIRA

View raw message