It is more the other way round. Servicemix is a distribution that
contains karaf, camel and cxf. So it is the easiest way to start working
with these projects together.
With a raw Karaf 2.2.x you currently have to replace the jre.properties
with jre.properties.cxf (both in etc dir). This sets the exports of the
system bundle in the way cxf and camel need them.
In Karaf 2.x you can then install camel and cxf with:
features:chooseurl camel 2.9.2
features:chooseurl cxf 2.6.1
The upcoming versions of Karaf (2.3.0 and 3.0.0) will make working with
Camel and CXF as easy as in Servicemix. The jre.properties does not have
to be changed anymore.
In Karaf 3 the syntax to install camel and cxf will change slightly:
feature:repo-add camel 2.9.2
feature:repo-add cxf 2.6.1
So installing camel and cxf is really easy even on a raw Karaf. A reason
to still use servicemix is that it is all in the distro so you do not
need an internet connection or a local maven repo.
Christian
This error comes from that system bundle 0 also export jaxb api package,
this doesn't happen in servicemix. Servicemix is fine-tuned with system
packages and other configuration so ensure it can support
camel/cxf/activemq OOTB.
Good to know. It also means I need to straighten out my understanding of
Karaf vs SMX :-(
I always assumed Karaf is a 'convenience' layer (offering stuff like a
shell, etc) on top of SMX...
And, thanks for SMX4-1204!
--
View this message in context:
http://servicemix.396122.n5.nabble.com/NMR-why-the-dependency-on-CXF-tp5714084p5714095.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
