RE: On another topic: Creating services programatically again

OK, that sounds like it may be a good approach. Could you point me to the Decanter code as a reference? Thanks, Scott -Original Message- From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net] Sent: Thursday, February 22, 2018 9:53 PM To: user@karaf.apache.org Subject: Re: On another to

Blueprint error: "name is already instanciated as null and cannot be removed"

Hello, I posted this in the Camel forum, but I have not received any answer, so I am trying here as well, since the error is coming from Blueprint. I am running Karaf 4.2.5, in trying to migrate my project to Camel 2.20.2 (from 2.17.4) I have blueprint configuration: http://www.osgi.

RE: Pax connection pools

Just another data point on this. Another reason I don't think Hikari is getting initialized. Note the pool name " HikariPool-9 - is starting". I always give my pools an explicit name, and the log message is using a Hikari default name. 2018-02-23T09:28:12,725 | INFO | CM Configuration Upda

Re: Blueprint error: "name is already instanciated as null and cannot be removed"

I wonder if this is related to https://github.com/apache/camel/commit/a4e94f036d02943814c84195d73837cf607c8c20 I suspect the call to camelContext.getComponent(component) should be replaced by camelContext.getComponent(component, false) in order to avoid the component to be auto-created. I'm in

Re: On another topic: Creating services programatically again

Rather than using a relatively low level api such as ManagedServiceFactory I’d suggest considering a ds component with configuration required and supplying it with factory configurations to get multiple instances. By using a configuration annotation you can have the configuration injected in a t

RE: On another topic: Creating services programatically again

That's exactly what I'm currently doing but I want to create instances of service from a factory and write the resulting configuration to .cfg. I need to do this so that I can save the configurations across Karaf installs. My app hierarchy resides outside of the Karaf installation so this work

Re: Blueprint error: "name is already instanciated as null and cannot be removed"

You are right, your proposed solution works. See my reply in the Camel forum. Best regards, Alex soto > On Feb 23, 2018, at 11:59 AM, Guillaume Nodet wrote: > > I wonder if this is related to > > https://github.com/apache/camel/commit/a4e94f036d02943814c84195d73837cf607c8c20 > >

Re: On another topic: Creating services programatically again

What do you mean by “create instances of service from a factory” and how would doing this result in a configuration at all? How are you proposing to replicate the configuration or .cfg file across multiple karaf instances? I’m not sure if or when karaf writes out a .cfg for a ca configuration cr

Deploying .kar file

hi, im having trouble with the features.xml file in a .kar app that im trying to deploy. My app depends on a couple of features int the cxf repository. Initially I installed these features manually with feature:add-repo cxf and feature:install *features i use*. I wanted to make it so that deploying

RE: On another topic: Creating services programatically again

That should have read "a service from a factory". To clarify, I have a component that is a factory (component), I create a new instance of the configuration and service using cfgAdmin.createFactoryConfiguration as shown below. I have a single Karaf instance but if I had multiple, since my hie

Re: On another topic: Creating services programatically again

I’m not sure what all of your code is doing. However, pre R7 you can’t specify the pid of a factory configuration. You might get the desired result by, on only one karaf instance, writing the .cfg file without creating a factory configuration yourself. David Jencks Sent from my iPhone > On F

RE: On another topic: Creating services programatically again

I should have clarified that this is running on Karaf 4.2 M2 so I suppose that's R7. The only issue with writing the .cfg myself and relying on Felix FileInstall to do its thing is that I really didn't want to have to wait for FIleInstall to hit its poll interval since the UI needs to update th

RE: On another topic: Creating services programatically again

The fundamental question is: What is the best way to create service instances (from a factory component) programmatically and store the associated configurations such that they persist across installations/upgrades of the platform, preferably using the facilities of the platform itself (ie. no

Re: On another topic: Creating services programatically again

Nothing R7 is released yet, the specs aren’t final, so I doubt very much that karaf implements any of it. I don’t think you’ve considered very many ramifications of what you’re proposing. In my experience an osgi web server has its port and interface configured via config admin, so you aren’t g

RE: On another topic: Creating services programatically again

Well, the ConfigurationAdmin.createFactoryConfiguration method call works in the version of ConfigurationAdmin that gets installed into Karaf 4.2M2, ie. a service gets created and is activated. If that's not what you're referring to, then I guess I'm misunderstanding. I currently only have 1 i

Re: On another topic: Creating services programatically again

Inline... Sent from my iPhone > On Feb 23, 2018, at 4:05 PM, Leschke, Scott wrote: > > Well, the ConfigurationAdmin.createFactoryConfiguration method call works in > the version of ConfigurationAdmin that gets installed into Karaf 4.2M2, ie. a > service gets created and is activated. If that