Re: Waiting for Namespace Handlers, even though they're available.

2013-08-31 Thread Tom Ellis
Hi yeah, Was about to update the solution here too, thanks Claus. On 31 August 2013 10:54, Claus Ibsen wrote: > Hi > > Okay found the thread on jboss forum where this was posted first > https://community.jboss.org/thread/232058 > > And Tom posted a solution on this forum. > > On Fri, Aug 30, 201

Re: Waiting for Namespace Handlers, even though they're available.

2013-08-31 Thread Claus Ibsen
Hi Okay found the thread on jboss forum where this was posted first https://community.jboss.org/thread/232058 And Tom posted a solution on this forum. On Fri, Aug 30, 2013 at 8:32 PM, Tom Ellis wrote: > I asked this on the JBoss Fuse forums, but I hope that maybe one of > you have come against

Re: Waiting for Namespace Handlers, even though they're available.

2013-08-31 Thread Claus Ibsen
Hi It depends what your bundle do. So if its in grace period it could be bacause your bundle uses an osgi service which is not yet available. Or you use a camel component which has not been installed yet. Are you sure you have installed all the needed Camel components first? eg you can install th

Re: Waiting for Namespace Handlers, even though they're available.

2013-08-30 Thread Tom Ellis
Changed the blueprint.xml header to http://www.osgi.org/xmlns/blueprint/v1.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.0.0"; xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0 http://www.osgi.org

Re: Waiting for Namespace Handlers, even though they're available.

2013-08-30 Thread John D. Ament
Try this In your blueprint.xml, the xsi:schemaLocation add http://camel.apache.org/schema/blueprint http://camel.apache.org/schema/blueprint/camel-blueprint-2.10.4.xsd and then in the body, http://camel.apache.org/schema/blueprint";> On Fri, Aug 30, 2013 at 2:32 PM, Tom Ellis wrote: > I asked