[jira] [Resolved] (KARAF-4363) ssh:sshd command shows default values twice
[ https://issues.apache.org/jira/browse/KARAF-4363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved KARAF-4363. - Resolution: Fixed > ssh:sshd command shows default values twice > --- > > Key: KARAF-4363 > URL: https://issues.apache.org/jira/browse/KARAF-4363 > Project: Karaf > Issue Type: Task > Components: karaf-shell >Affects Versions: 3.0.6, 4.0.4 >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Trivial > Fix For: 4.1.0, 4.0.5, 3.0.7 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4363) ssh:sshd command shows default values twice
[ https://issues.apache.org/jira/browse/KARAF-4363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15168610#comment-15168610 ] ASF subversion and git services commented on KARAF-4363: Commit 600f0b44d7eafe66dda3258f16f24d977f68d330 in karaf's branch refs/heads/karaf-3.0.x from [~ancosen] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=600f0b4 ] [KARAF-4363] ssh:sshd command shows default values twice > ssh:sshd command shows default values twice > --- > > Key: KARAF-4363 > URL: https://issues.apache.org/jira/browse/KARAF-4363 > Project: Karaf > Issue Type: Task > Components: karaf-shell >Affects Versions: 3.0.6, 4.0.4 >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Trivial > Fix For: 4.1.0, 4.0.5, 3.0.7 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4363) ssh:sshd command shows default values twice
[ https://issues.apache.org/jira/browse/KARAF-4363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15168605#comment-15168605 ] ASF subversion and git services commented on KARAF-4363: Commit e5fc4472fc902c9871069c93880e5628c80e39ec in karaf's branch refs/heads/karaf-4.0.x from [~ancosen] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=e5fc447 ] [KARAF-4363] ssh:sshd command shows default values twice > ssh:sshd command shows default values twice > --- > > Key: KARAF-4363 > URL: https://issues.apache.org/jira/browse/KARAF-4363 > Project: Karaf > Issue Type: Task > Components: karaf-shell >Affects Versions: 3.0.6, 4.0.4 >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Trivial > Fix For: 4.1.0, 4.0.5, 3.0.7 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4363) ssh:sshd command shows default values twice
[ https://issues.apache.org/jira/browse/KARAF-4363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15168596#comment-15168596 ] ASF subversion and git services commented on KARAF-4363: Commit 47024fbf2398e2da2567fdcfd5afd4230bae7eac in karaf's branch refs/heads/master from [~ancosen] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=47024fb ] [KARAF-4363] ssh:sshd command shows default values twice > ssh:sshd command shows default values twice > --- > > Key: KARAF-4363 > URL: https://issues.apache.org/jira/browse/KARAF-4363 > Project: Karaf > Issue Type: Task > Components: karaf-shell >Affects Versions: 3.0.6, 4.0.4 >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Trivial > Fix For: 4.1.0, 4.0.5, 3.0.7 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4363) ssh:sshd command shows default values twice
Andrea Cosentino created KARAF-4363: --- Summary: ssh:sshd command shows default values twice Key: KARAF-4363 URL: https://issues.apache.org/jira/browse/KARAF-4363 Project: Karaf Issue Type: Task Components: karaf-shell Affects Versions: 4.0.4, 3.0.6 Reporter: Andrea Cosentino Assignee: Andrea Cosentino Priority: Trivial Fix For: 4.1.0, 4.0.5, 3.0.7 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4362) Improve the maven assembly goal so that it can run at package phase instead of install phase
Guillaume Nodet created KARAF-4362: -- Summary: Improve the maven assembly goal so that it can run at package phase instead of install phase Key: KARAF-4362 URL: https://issues.apache.org/jira/browse/KARAF-4362 Project: Karaf Issue Type: Improvement Components: karaf-tooling Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: 4.1.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[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. For example we would like to make
it possible to have retrieve properties coming from another framework such as
Spring and use those to override config.properties settings in a dynamic way,
without needing to dump them to a file at Karaf startup. I'm aware of the
${includes} and ${optionals} but those require files to be read from the disk
where here I'm talking about being able to dynamically manipulate the
properties once loaded.
Basically something like this would be fantastic
{code}
// code to setup System properties
main = new Main(new String[0]);
ConfigProperties config = main.getConfig();
if (config == null) {
config = new ConfigProperties();
}
// manipulate config in any way desired
main.setConfig(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. For example we would like to make
it possible to have calculate properties that override the values of the
config.properties settings in a dynamic way. I'm aware of the ${includes} and
${optionals} but those require files to be read from the disk where here I'm
talking about being able to dynamically manipulate the properties once loaded.
Basically something like this would be fantastic
{code}
// code to setup System properties
main = new Main(new String[0]);
ConfigProperties config = main.getConfig();
if (config == null) {
config = new ConfigProperties();
}
// manipulate config in any way desired
main.setConfig(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.
> 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
> Attachments:
> KARAF_4361_Allow_dynamic_config_customization_when_embedding_Karaf_using_the_Main_class.patch
>
>
> 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
[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. For example we would like to make
it possible to have "custom.properties" files that could override the values of
the config.properties settings so that we can offer integrators to modify a
custom file without touching the default file.
Basically something like this would be fantastic
{code}
// code to setup System properties
main = new Main(new String[0]);
ConfigProperties config = main.getConfig();
if (config == null) {
config = new ConfigProperties();
}
// manipulate config in any way desired
main.setConfig(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.getConfig();
if (config == null) {
config = new ConfigProperties();
}
// manipulate config in any way desired
main.setConfig(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.
> 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
> Attachments:
> KARAF_4361_Allow_dynamic_config_customization_when_embedding_Karaf_using_the_Main_class.patch
>
>
> 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. For example we would like to
> make it possible to have "custom.properties" files that could override the
> values of the config.properties settings so that we can offer integrators to
> modify a custom file without touching the default file.
> Basically something like this would be fantastic
> {code}
> // code to setup System properties
> main = new Main(new String[0]);
> ConfigProperties config = main.getConfig();
> if (config == null) {
>config = new ConfigProperties();
>
[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. For example we would like to make
it possible to have calculate properties that override the values of the
config.properties settings in a dynamic way. I'm aware of the ${includes} and
${optionals} but those require files to be read from the disk where here I'm
talking about being able to dynamically manipulate the properties once loaded.
Basically something like this would be fantastic
{code}
// code to setup System properties
main = new Main(new String[0]);
ConfigProperties config = main.getConfig();
if (config == null) {
config = new ConfigProperties();
}
// manipulate config in any way desired
main.setConfig(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. For example we would like to make
it possible to have "custom.properties" files that could override the values of
the config.properties settings so that we can offer integrators to modify a
custom file without touching the default file.
Basically something like this would be fantastic
{code}
// code to setup System properties
main = new Main(new String[0]);
ConfigProperties config = main.getConfig();
if (config == null) {
config = new ConfigProperties();
}
// manipulate config in any way desired
main.setConfig(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.
> 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
> Attachments:
> KARAF_4361_Allow_dynamic_config_customization_when_embedding_Karaf_using_the_Main_class.patch
>
>
> 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. For example we would like to
> make it possible to have calculate properties that override the values of the
> config.properties settings in a dynamic way. I'm aware of the ${includes} and
>
[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:
---
Attachment:
KARAF_4361_Allow_dynamic_config_customization_when_embedding_Karaf_using_the_Main_class.patch
I've attached a patch I generated against the Karaf 4.0.x that implements the
getter and setter for the config variable and also modified the launch method
to check if the variable is null and only set it up when it is null.
In effect this shouldn't change the contract for existing uses, but should make
it possible to access and modify the config properties setup before the launch
is called.
> 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
> Attachments:
> KARAF_4361_Allow_dynamic_config_customization_when_embedding_Karaf_using_the_Main_class.patch
>
>
> 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.getConfig();
> if (config == null) {
>config = new ConfigProperties();
> }
> // manipulate config in any way desired
> main.setConfig(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)
[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.getConfig();
if (config == null) {
config = new ConfigProperties();
}
// manipulate config in any way desired
main.setConfig(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();
if (config == null) {
config = new ConfigProperties();
}
// 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.
> 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.getConfig();
> if (config == null) {
>config = new ConfigProperties();
> }
> // manipulate config in any way desired
> main.setConfig(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)
[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();
if (config == null) {
config = new ConfigProperties();
}
// 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}
Btw we are using Karaf 4.0.x so having this in both Karaf 4.1.0 and Karaf 4.0
would be fantastic.
> 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();
> if (config == null) {
>config = new ConfigProperties();
> }
> // 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)
[jira] [Created] (KARAF-4361) Allow dynamic config customization when embedding Karaf using the Main class
Serge Huber created KARAF-4361:
--
Summary: 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.0.4, 4.1.0
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}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[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)
[jira] [Commented] (KARAF-4351) [RBAC] Optimize access to JMXSecurityMBean.canInvoke(Map)
[
https://issues.apache.org/jira/browse/KARAF-4351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15166995#comment-15166995
]
ASF subversion and git services commented on KARAF-4351:
Commit e96633f09bda58f24db980e21ddba149d9e58e74 in karaf's branch
refs/heads/karaf-2.x from [~gzres]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=e96633f ]
[KARAF-4351] Optimize ConfigAdmin access in bulk RBAC calls
(cherry picked from commit 8c8dffdc2e0439e099b865bc4a2b8cd4614cd2a2)
> [RBAC] Optimize access to JMXSecurityMBean.canInvoke(Map)
> -
>
> Key: KARAF-4351
> URL: https://issues.apache.org/jira/browse/KARAF-4351
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-security
>Affects Versions: 2.4.4, 3.0.6, 4.0.4
>Reporter: Grzegorz Grzybek
>
> We've scenario where there are 2000 ActiveMQ queues running in Karaf with
> hawtio that leverages RBAC.
> hawtio, through Jolokia library calls
> {{org.apache.karaf.management.JMXSecurityMBean#canInvoke(java.util.Map)}}
> method passing map of >2000 MBeanNames to lists of average size = 20.
> Thus we have >4 calls to one of
> {{org.apache.karaf.management.internal.JMXSecurityMBeanImpl#canInvoke()}}
> methods for pairs of MBean+signature and we have equal number of calls to
> {{org.osgi.service.cm.ConfigurationAdmin#listConfigurations("(service.pid=jmx.acl*)"}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4351) [RBAC] Optimize access to JMXSecurityMBean.canInvoke(Map)
[
https://issues.apache.org/jira/browse/KARAF-4351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15166996#comment-15166996
]
ASF subversion and git services commented on KARAF-4351:
Commit 5b29a4466165b519637b9aa9e0b9c3bf0794b7b9 in karaf's branch
refs/heads/karaf-2.x from [~gzres]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=5b29a44 ]
[KARAF-4351] Optimize JAAS ACC/Subject access in bulk RBAC calls
(cherry picked from commit fe2a82b1bc12c91e8f61e8ec1dc237e09aa0052c)
> [RBAC] Optimize access to JMXSecurityMBean.canInvoke(Map)
> -
>
> Key: KARAF-4351
> URL: https://issues.apache.org/jira/browse/KARAF-4351
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-security
>Affects Versions: 2.4.4, 3.0.6, 4.0.4
>Reporter: Grzegorz Grzybek
>
> We've scenario where there are 2000 ActiveMQ queues running in Karaf with
> hawtio that leverages RBAC.
> hawtio, through Jolokia library calls
> {{org.apache.karaf.management.JMXSecurityMBean#canInvoke(java.util.Map)}}
> method passing map of >2000 MBeanNames to lists of average size = 20.
> Thus we have >4 calls to one of
> {{org.apache.karaf.management.internal.JMXSecurityMBeanImpl#canInvoke()}}
> methods for pairs of MBean+signature and we have equal number of calls to
> {{org.osgi.service.cm.ConfigurationAdmin#listConfigurations("(service.pid=jmx.acl*)"}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
