I meant my own OSGi services that I register and pull from the registry. Not Camel core components.
Trust me I don't have a great love of Blueprint but I haven't seen any solutions using DS and Camel that I thought were "ooh, I just have to do it that way". On Fri, Jul 8, 2016 at 6:14 AM, Christian Schneider <ch...@die-schneider.net > wrote: > > proxies ensure that Camel has what it needs when it runs > > Unfortunately this is not true. Camel only runs well because the defined > start levels start the components before your user bundles. This is a very > fragile approach though and totally breaks when not using karaf. The core > of the problem is that in camel you access a component by just a String > uri. If the component is present at the time the route starts then this > will work if not it will break. > As the dependency to the component is just a URI there is no way to use > static code analysis to make sure all necessary components are present. So > I am not sure how to solve this. > > Christian > > On 08.07.2016 13:05, Brad Johnson wrote: > >> Christian, >> >> Perhaps that's why my view of DS isn't as sunny as it could be since I >> use Camel extensively and did not have great experiences with it and DS. >> While I know that proxies have their downside and that chaining is >> preferable, proxies ensure that Camel has what it needs when it runs. When >> I fire up Fuse with 800 bundles the thought of having to manage start up >> orders as one more configuration chore is a bit depressing. >> >> I'm very much looking forward to when I can do more work with Karaf 4 and >> profiles. For most of my clients they are in Fuse back in 2.x however. >> >> Brad >> >> > -- > Christian Schneider > http://www.liquid-reality.de > > Open Source Architect > http://www.talend.com > >
