camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <>
Subject Re: Karaf vs Servicemix 4.x
Date Wed, 02 Nov 2011 14:25:14 GMT
On Tue, Nov 1, 2011 at 10:55 PM, boday <> wrote:
> my take is that unless you explicitly need any Servicemix features, then just
> use Karaf because its lighter weight, etc...

Karaf is a general purpose container which is not preset/preconfigured
for optimal Camel runtime. You would need to configure this yourself.

Apache ServiceMix is a one stop solution that incorporates CXF, AMQ,
Camel, etc. in a known and stable working set.
If you assemble Karaf + Camel + CXF etc yourself then you can run into
issues and whatnot.

That said over the recent time Karaf have improved to better cater for
feature version ranges, etc.
But you can be on a big goose hunt to fiddle with and
whatnot to comment in/out various API from the JDK to get anything
working on Karaf.

Apache ServiceMix 5 will become much ligher when we ditch the JBI
baggage, and in the upcoming 4.4 release Apache ServiceMix (AFAIK)
offers different profiles, so you can have a light, medium, full

> diwakar wrote:
>> Hi,
>>           Thanks for the replies.
>> has
>>           >> the two primary reason for using ServiceMix is if you want
>> an ESB, 2) NMR (a feature that allows you to community between bundles AND
>> instances of Karaf)
>>           AFAIK Camel does not use servicemix NMR and Camel itself is like
>> an ESB.
>>           It is still not clear how hosting Camel in Servicemix 4.x is
>> better than Karaf.
>> With Best Regards,
>> Diwakar
> -----
> Ben O'Day
> IT Consultant -
> --
> View this message in context:
> Sent from the Camel - Users mailing list archive at

Claus Ibsen
Twitter: davsclaus, fusenews
Author of Camel in Action:

View raw message