Running mvn dependency:tree in quickstarts/blueprint-camel-drools-decision-table and others, I can see that two versions of CXF are actually on the classpath:

3.1.5.redhat-630069
org.apache.cxf:cxf-core:jar:3.1.5.redhat-630069

• vs. -

2.7.18
org.apache.cxf:cxf-rt-core:jar:2.7.18

Trying the similar with BxMS 6.3.1 CR1 and Integration Pack 1.4.0.redhat-630024, I get similar output (note cxf-core vs. cxf-rt-frontend-jaxrs versions):

[INFO] +- org.jboss.integration.fuse:kie-camel:jar:1.4.0.redhat-630024:compile
[INFO] |  +- org.apache.camel:camel-core:jar:2.17.0.redhat-630069:compile
...
[INFO] |  +- org.apache.camel:camel-cxf:jar:2.17.0.redhat-630069:compile
[INFO] |  |  +- org.apache.camel:camel-cxf-transport:jar:2.17.0.redhat-630069:compile
[INFO] |  |  |  \- javax.servlet:javax.servlet-api:jar:3.1.0:compile
[INFO] |  |  \- org.apache.cxf:cxf-rt-rs-security-oauth:jar:2.7.18.redhat-1:compile
[INFO] |  |     \- net.oauth.core:oauth-provider:jar:20100527:compile
[INFO] |  |        \- net.oauth.core:oauth:jar:20100527:compile
[INFO] |  +- org.apache.camel:camel-xstream:jar:2.17.0.redhat-630069:runtime
[INFO] |  +- org.apache.cxf:cxf-core:jar:3.1.5.redhat-630069:compile
[INFO] |  +- org.apache.cxf:cxf-rt-frontend-jaxrs:jar:2.7.18.redhat-1:compile
...

After discussion with psiroky_jira, we concluded that CXF changed artifact GAV between version 2 and 3 - in 3.x, there is probably no cxf-api and there is cxf-core artifact.

The quickstarts poms should include an exclusion of undesired CXF dependencies; in case of EAP quickstarts, we do not want CXF 3.x cxf-core artifact on the classpath, while in Karaf quickstarts, we do not want CXF 2.x cxf-api and other artifacts.

The quickstarts should then serve as a reference for users how to setup their pom.xml when using Integration Pack with BxMS.