As CXF supports lots of other API, just one simpel cxf-api and cxf-core
can't provides what we want to in camel-cxf :(
Christian, I checked the camel-cxf pom.xml, if you want to use the CXF
mini bundle , you just need to exclude below module, but you may need to
add some other third part dependencies to let CXF run.
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-cxf</artifactId>
<version>${camel-version}</version>
<exclusions>
<exclusion>
<groupId>org.apache.cxf</groupId>
<artifactId>cxf-rt-frontend-jaxrs</artifactId>
</exclusion>
<exclusion>
<groupId>org.apache.cxf</groupId>
<artifactId>cxf-rt-frontend-jaxws</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>org.apache.cxf</groupId>
<artifactId>cxf-bundle-minimal</artifactId>
<version>${cxf-version}</version>
</dependency>
Willem
Christian Schneider wrote:
While I think it is great that a mini bundle is there for some special
cases I think it should possible to make the modular version more
independent of external libs. Especially the cxf api and core should
have no dependencies. Spring and camel have also achieved this. Having
said this I know it is a lot of work ;-(
Greetings
Christian
Am 21.01.2010 11:10, schrieb Willem Jiang:
Just a quick note for camel-cxf module:
There are more than 4 components in the camel-cxf
cxf, cxfrs, cxfbeans, camel transport for cxf , and an unused soap
component.
I think we just put them into camel-cxf module because they are CXF
related, if there are many people complain about it introduces lots of
third party dependencies we could consider to split them.
BTW, CXF has a mini bundle which removed more than 20 of cxf modules
and can be used in most case, maybe we could consider to use it.
Willem
