hi smalik, it is true as Sergey mentioned that the current camel-cxf 2.15.x brings both jaxws and jaxrs minimal requirements and that is too much when you want to use only one or the other.
But you still won't be needing a hundred of jars to just run a plain soap based service call, though. When using cxf-3.0.6 with camel-2.15.3, a minimal camel file to cxf soap call scenario using spring will need something like this: [INFO] +- org.apache.camel:camel-cxf:jar:2.15.3:compile [INFO] | +- org.apache.camel:camel-core:jar:2.15.3:compile [INFO] | | \- org.slf4j:slf4j-api:jar:1.6.6:compile [INFO] | +- org.apache.camel:camel-cxf-transport:jar:2.15.3:compile [INFO] | +- org.apache.cxf:cxf-rt-frontend-jaxrs:jar:3.0.6:compile [INFO] | | +- org.apache.cxf:cxf-core:jar:3.0.6:compile [INFO] | | | +- org.codehaus.woodstox:woodstox-core-asl:jar:4.4.1:compile [INFO] | | | | \- org.codehaus.woodstox:stax2-api:jar:3.1.4:compile [INFO] | | | \- org.apache.ws.xmlschema:xmlschema-core:jar:2.2.1:compile [INFO] | | +- javax.ws.rs:javax.ws.rs-api:jar:2.0.1:compile [INFO] | | +- javax.annotation:javax.annotation-api:jar:1.2:compile [INFO] | | \- org.apache.cxf:cxf-rt-transports-http:jar:3.0.6:compile [INFO] | +- org.apache.cxf:cxf-rt-frontend-jaxws:jar:3.0.6:compile [INFO] | | +- xml-resolver:xml-resolver:jar:1.2:compile [INFO] | | +- asm:asm:jar:3.3.1:compile [INFO] | | +- org.apache.cxf:cxf-rt-bindings-xml:jar:3.0.6:compile [INFO] | | \- org.apache.cxf:cxf-rt-frontend-simple:jar:3.0.6:compile [INFO] | +- org.apache.cxf:cxf-rt-rs-security-oauth:jar:3.0.6:compile [INFO] | | +- org.apache.cxf:cxf-rt-rs-client:jar:3.0.6:compile [INFO] | | \- net.oauth.core:oauth-provider:jar:20100527:compile [INFO] | | \- net.oauth.core:oauth:jar:20100527:compile [INFO] | +- org.springframework:spring-core:jar:4.1.6.RELEASE:compile [INFO] | | \- commons-logging:commons-logging:jar:1.2:compile [INFO] | +- org.apache.cxf:cxf-rt-bindings-soap:jar:3.0.6:compile [INFO] | | +- org.apache.cxf:cxf-rt-wsdl:jar:3.0.6:compile [INFO] | | | \- wsdl4j:wsdl4j:jar:1.6.3:compile [INFO] | | \- org.apache.cxf:cxf-rt-databinding-jaxb:jar:3.0.6:compile [INFO] | +- com.sun.xml.bind:jaxb-core:jar:2.2.11:compile [INFO] | \- com.sun.xml.bind:jaxb-impl:jar:2.2.11:compile [INFO] +- org.apache.camel:camel-spring:jar:2.15.3:compile [INFO] | +- org.springframework:spring-aop:jar:4.1.6.RELEASE:compile [INFO] | | \- aopalliance:aopalliance:jar:1.0:compile [INFO] | \- org.springframework:spring-tx:jar:4.1.6.RELEASE:compile [INFO] +- org.springframework:spring-context:jar:3.2.13.RELEASE:compile [INFO] | \- org.springframework:spring-expression:jar:3.2.13.RELEASE:compile [INFO] \- org.springframework:spring-beans:jar:3.2.13.RELEASE:compile 2015-09-08 19:25 GMT+02:00 smalik <sarfraz.ma...@rabobank.com>: > Thanks Sergey. > > Unfortunately I can't wait long enough for Camel 2.16 I have a delivery > pretty soon :) > > Ok so indeed the camel-cxf stuff looks quite bloated for my purposes. > > Do you know of any other (lightweight) Camel endpoint I can use for the > purpose of sending a POJO to a webservice? http, restlet? Or maybe I'll have > to write my own Camel endpoint. The service I am calling is provided by Axis > 2, unfortunately there is no axis endpoint in camel, apparently it got > replaced by the bloated cxf! > > cheers > > > > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/CXF-too-many-dependencies-tp5771344p5771350.html > Sent from the Camel Development mailing list archive at Nabble.com.