It looks like (one of) the block of code in the route that is causing the 
BlueprintContainer to not start is
                <json library="Jackson"
                      unmarshalTypeName="<my-class-name> "/>

Does unmarshalling require some import that I'm not including? Again, the works 
when running in a real Karaf container, but it does not work when I'm using the 


-----Original Message-----
From: Tadayoshi Sato [] 
Sent: Monday, February 12, 2018 6:08 PM
Subject: Re: "Gave up waiting for BlueprintContainer" when using 


Typically it happens on CamelBlueprintTestSupport when you omit some OSGi 
dependencies in pom.xml: It's not just Maven dependencies but also OSGi bundle 
imports/exports. Typically a successful camel blueprint test has a felix 
maven-bundle-plugin configuration and the import/export packages declarations 
like these:

Hope this helps.

On Tue, Feb 13, 2018 at 9:41 AM, Harrison Tarr <>

> Hi,
> I just heard about "camel-test-blueprint" today and I started using 
> it. I was able to get a feel for it by using a contrived Camel route 
> in a blueprint.xml and everything worked as expected. I'm now trying 
> to test "real" camel routes in my products blueprint.xml, but I'm 
> getting a
> RuntimeException: "Gave up waiting for BlueprintContainer". Any ideas 
> what causes that? I'm at a loss, even after Google.
> Best Regards,
> Harrison Tarr

Reply via email to