On Thu, Sep 17, 2009 at 9:25 AM, TheWinch <[email protected]> wrote: > > Very strange behaviour. > I just stopped servicemix and restarted it (without clearing the bundles > cache) and .... booom, the component seems to work ! > > I think my issue is more related to the Karaf container than to Camel. The > fact is at the beginning my component had some missing dependencies, that I > fixed. I kept updating the bundle. I even uninstalled/reinstalled it... but > whithout restarting ServiceMix. Looking at the source where the NPE occurs, > I see this: > > 82 BundleContext bundleContext = > Activator.getBundle().getBundleContext(); > 83 > 84 URL url; > 85 for (Bundle bundle : bundleContext.getBundles()) { > > So it seems that Karaf somehow did start the bundle with a NULL bundle > context. Very strange..... > > However now it works. Any idea where I could report my bug at best ?
At ServiceMix User forum is a good spot. Willem Jiang is a committer at both SMX and Camel and works with OSGi and other stuff so he is an excellent candidate to look into this. But it could very well be a more general problem with hot deploying bundles. I recall similar issues that manifest in other errors that are remedied by restarting SMX. So I think its being looked into. > -- > View this message in context: > http://www.nabble.com/Error-using-camel-file-with-windows-tp25475829p25486384.html > Sent from the Camel - Users mailing list archive at Nabble.com. > > -- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
