The wildcard conduit setting should work. You can find an example here[1][2].
BTW, I fill a JIRA[3] for setting the conduit in a programmatic way. [1]https://github.com/apache/camel/blob/master/components/camel-cxf/src/test/java/org/apache/camel/component/cxf/CxfTimeoutTest.java [2]https://github.com/apache/camel/blob/master/components/camel-cxf/src/test/resources/org/apache/camel/component/cxf/cxfConduitTimeOutContext.xml [3]https://issues.apache.org/jira/browse/CAMEL-7845 -- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On September 24, 2014 at 3:13:03 AM, jjathman ([email protected]) wrote: > Thanks for the help, I will have to check out using the header override. > Thank you! > > I found that the real problem I was having with the conduits is that it > doesn't seem like Camel is respecting the *.http-conduit wildcard pattern > for outgoing CXF connections. When I replace that wildcard with the specific > names of the conduits then it does work how I would expect. For whatever > reason, if the name is a wildcard the conduit isn't used. This seems like a > bug to me. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Programmatic-CXF-Endpoint-tp5756368p5756914.html > > Sent from the Camel - Users mailing list archive at Nabble.com. >
