The blueprint deployer does not have any namespace extension. It registers an URL handler for the "blueprint" protocol, but I don't remember the jbi deployer using it in any way.
On Fri, Jun 25, 2010 at 03:04, Daniel Kulp <[email protected]> wrote: > > I spent a good deal of time today and yesterday trying to figure out why some > endpoints and components were not starting up. It turns out, I didn't have > the org.apache.felix.karaf.deployer.blueprint bundle installed. The JBI > components (particularly the deployer in my case) apparently now require it as > their blueprint files have extensions that reference it's namespace. > > The questions is: should the JBI bundles have a "Required-Bundle" for the > deployer.bundle? Without it, the bundle seemed to start, but not really. Does that really solve the problems ? I don't find why this bundle would have an impact. > On a related note, the deployer.blueprint bundle is REALLY sensitive to order > and timing issues with the blueprint bundle. Blueprint seems to start some > of it's stuff on a timer thread. If deployer.blueprint starts before that > timer triggers, it doesn't seem to register correctly. My workaround was to > put a bunch of bundles between them. Kind of a hack. Yeah. I can imagine seeing some startup dependencies problems as you describe when using spring-dm, because there's actually no expressed dependencies between a spring app and the namespaces it require. But with blueprint, i've specifically enhanced the aries implementation to behave correctly and wait until the required namespaces are available before actually starting the application. Could you please provide more informations about the problem ? What actually happen? > > -- > Daniel Kulp > [email protected] > http://dankulp.com/blog > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
