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

I will take a look on this today or tomorrow. Regards JB On 02/23/2018 05:59 PM, Guillaume Nodet wrote: > I wonder if this is related to  >     > https://github.com/apache/camel/commit/a4e94f036d02943814c84195d73837cf607c8c20 > > I suspect the call to camelContext.getComponent(component)  should

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: 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

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.