Raul Kripalani wrote
> It can be seen in your logs that your bundle my.test.core.service starts
> before camel-cxf. That's clearly the cause of the problem.
>
> Increasing the start level of my.test.core.service to a number above
> camel-cxf's will help.
>
> Regards,
> Raúl.
> On 31 May 2013 15:5
It can be seen in your logs that your bundle my.test.core.service starts
before camel-cxf. That's clearly the cause of the problem.
Increasing the start level of my.test.core.service to a number above
camel-cxf's will help.
Regards,
Raúl.
On 31 May 2013 15:58, "Smith-John" wrote:
> Raul Kripala
Raul Kripalani wrote
> Hi,
>
> I've seen this before too, but I never had the time to drill into it.
>
> It generally works fine, but in 1 out of 50 cases, most of my bundles fail
> to start claiming that X component was not found. Route start levels are
> higher than camel-core and component bun
Hi,
I've seen this before too, but I never had the time to drill into it.
It generally works fine, but in 1 out of 50 cases, most of my bundles fail
to start claiming that X component was not found. Route start levels are
higher than camel-core and component bundles. And there's no Spring or
Blue
