[camel-cxf] Migration to 3.18 BLOCKED due to 404 NOT FOUND on new schemas URLs

2022-08-03 Thread (Ext.) Ugur Kurnaz
Hello, Referring to migration guide https://camel.apache.org/manual/camel-3x-upgrade-guide-3_18.html#_camel_cxf, we need to use new namespace/schemas url for jaxrs/jaxws endpoint definitions : Old Namespace New Namespace http://camel.apache.org/schema/cxf http://camel.apache.org/schema/cxf

Re: [camel-cxf] Migration to 3.18 BLOCKED due to 404 NOT FOUND on new schemas URLs

2022-08-03 Thread Claus Ibsen
Hi Thanks. The XSD files are in the released JARs so you can find them there curerntly. On Wed, Aug 3, 2022 at 4:00 PM (Ext.) Ugur Kurnaz wrote: > Hello, > > Referring to migration guide > https://camel.apache.org/manual/camel-3x-upgrade-guide-3_18.html#_camel_cxf, > we need to use new name

FW: Upgrade to Apache Camel 3 - no longer get logging / stacktrace

2022-08-03 Thread Snaith, Douglas
I've had a couple of suggestions which either haven't worked or don't seem applicable. My specific problem is a camel route that calls a SOAP endpoint, using cxf. We used to get a stacktrace and exchange messages when the call failed, but no longer. We need those in case the soap endpoint goes

Re: FW: Upgrade to Apache Camel 3 - no longer get logging / stacktrace

2022-08-03 Thread Claus Ibsen
For CXF you need to turn on stacktraces if you want to expose that. https://cxf.apache.org/docs/debugging-and-logging.html See also (search for stacktrace) https://camel.apache.org/components/3.18.x/cxf-component.html On Wed, Aug 3, 2022 at 6:48 PM Snaith, Douglas wrote: > I’ve had a couple of

Log XPath

2022-08-03 Thread Simon Martinelli
Hi, How can I log an xpath? This is not possible: .log("xpath("//name") As a workaround I use: .setHeader("xpath", xpath("//name")) .log(${headers.xpath}") But this doesn't feel right. Any help is appreciated Simon