OH, I know the key of the issue. camel-cxf doesn’t support to setup the path as the camel-cxfrs does.
Why do you need to send the request with a dynamic sub path? -- 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 June 21, 2014 at 9:51:14 PM, bocamel ([email protected]) wrote: > I have a cxf web services endpoint (cxf:bean:myservice) that expects to > receive requests to localhost/myservice, i.e. address = > https://0.0.0.0/myservice. Of course, it will also receive anything under > this path, e.g. localhost/myservice/*. > > I want to send requests to this cxf endpoint with a dynamic subpath, e.g. > localhost/myservice/customer1. I tried to set the CamelHttpPath (to > "customer1") as one of the headers when calling > pTemplate.sendBodyAndHeaders("cxf:bean:myservice", body, headers). But the > subpath is ignored and the consumer only sees the main path. Is there a way > to do this using the existing cxf endpoint, or I have to use camel-http to > build the HTTP call? > > Any help will be greatly appreciated. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Cannot-supply-CamelHttpPath-to-a-call-to-a-CXF-endpoint-tp5752657.html > > Sent from the Camel - Users mailing list archive at Nabble.com. >
