Re: CamelNamespaceHandler and CAMEL-9570

I created a PR that fixes the issue - hopefully some other OSGi guys will comment on this. The PR is for CAMEL-9570 -https://github.com/apache/camel/pull/1269 > On Nov 11, 2016, at 1:38 PM, Quinn Stevenson > wrote: > > I can put together a PR,

Re: CamelNamespaceHandler and CAMEL-9570

I can put together a PR, but the more I look at this, the more I think this specific class isn’t needed. It’s trying to register service references, but the service references should already be there IMO. I know I wouldn’t want Camel to automatically find some service I wasn’t expecting it to

Re: CamelNamespaceHandler and CAMEL-9570

Hi I think that dependency stuff was created to ensure Camel would detect which other karaf features it depends upon and then graceful wait for those, instead of fail to startup. I think it was gnodet whom had this idea and created the initial implementation. Not sure if he or other OSGi guys go

Re: CamelNamespaceHandler and CAMEL-9570

After messing with this for quite a while, I know what is causing CAMEL-9570. The CamelNamespaceHandler registers and instance of the CamelNamespaceHandler$CamelDependenciesFinder as an Aries ComponentDefinitionRegistryProcessor, which is fine. However, the CamelDependenciesFinder.process() me

CamelNamespaceHandler and CAMEL-9570

I’ve managed to narrow down the code that causes the issue described in CAMEL-9570 ( https://issues.apache.org/jira/browse/CAMEL-9570 ). If I remove the following lines in the CamelNamespaceHandler class (parseCamelContextNode method), it corre