You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Serge Huber (JIRA)" <ji...@apache.org> on 2016/02/25 16:43:18 UTC
[jira] [Updated] (KARAF-4361) Allow dynamic config customization
when embedding Karaf using the Main class
[ https://issues.apache.org/jira/browse/KARAF-4361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Serge Huber updated KARAF-4361:
-------------------------------
Description:
We are using Karaf by embedding it and basically starting it like this :
{code}
// code to setup System properties
main = new Main(new String[0]);
main.launch();
{code}
The problem is that the ConfigProperties that are used to startup Karaf are directly created in the main.launch() method, like this:
{code}
public void launch() throws Exception {
config = new ConfigProperties();
{code}
Ideally it would be great if we could either have a setter to provide the config value, so that we could manipulate it before launching. In an embedded environment this quickly becomes a necessity.
Basically something like this would be fantastic
{code}
// code to setup System properties
main = new Main(new String[0]);
ConfigProperties config = main.getConfigProperties();
// manipulate config in any way desired
main.setConfigProperties(config)
main.launch();
{code}
The main.launch could then simply be modified to something like this :
{code}
public void launch() throws Exception {
if (config == null) {
config = new ConfigProperties();
}
{code}
Btw we are using Karaf 4.0.x so having this in both Karaf 4.1.0 and Karaf 4.0 would be fantastic.
was:
We are using Karaf by embedding it and basically starting it like this :
{code}
// code to setup System properties
main = new Main(new String[0]);
main.launch();
{code}
The problem is that the ConfigProperties that are used to startup Karaf are directly created in the main.launch() method, like this:
{code}
public void launch() throws Exception {
config = new ConfigProperties();
{code}
Ideally it would be great if we could either have a setter to provide the config value, so that we could manipulate it before launching. In an embedded environment this quickly becomes a necessity.
Basically something like this would be fantastic
{code}
// code to setup System properties
main = new Main(new String[0]);
ConfigProperties config = main.getConfigProperties();
// manipulate config in any way desired
main.setConfigProperties(config)
main.launch();
{code}
The main.launch could then simply be modified to something like this :
{code}
public void launch() throws Exception {
if (config == null) {
config = new ConfigProperties();
}
{code}
> Allow dynamic config customization when embedding Karaf using the Main class
> ----------------------------------------------------------------------------
>
> Key: KARAF-4361
> URL: https://issues.apache.org/jira/browse/KARAF-4361
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-core
> Affects Versions: 4.1.0, 4.0.4
> Reporter: Serge Huber
>
> We are using Karaf by embedding it and basically starting it like this :
> {code}
> // code to setup System properties
> main = new Main(new String[0]);
> main.launch();
> {code}
> The problem is that the ConfigProperties that are used to startup Karaf are directly created in the main.launch() method, like this:
> {code}
> public void launch() throws Exception {
> config = new ConfigProperties();
> {code}
> Ideally it would be great if we could either have a setter to provide the config value, so that we could manipulate it before launching. In an embedded environment this quickly becomes a necessity.
> Basically something like this would be fantastic
> {code}
> // code to setup System properties
> main = new Main(new String[0]);
> ConfigProperties config = main.getConfigProperties();
> // manipulate config in any way desired
> main.setConfigProperties(config)
> main.launch();
> {code}
> The main.launch could then simply be modified to something like this :
> {code}
> public void launch() throws Exception {
> if (config == null) {
> config = new ConfigProperties();
> }
> {code}
> Btw we are using Karaf 4.0.x so having this in both Karaf 4.1.0 and Karaf 4.0 would be fantastic.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)