Hi On Mon, Jul 18, 2011 at 1:03 PM, akuhtz <[email protected]> wrote: > Hi, > > I was trying to use the new transform feature for CXF > (http://cxf.apache.org/docs/transformationfeature.html) but limited luck > until now. > > It works fine if you try to replace a namespace for a soap body element, > that's the good news. But if a namespace is replaced in a soap header > element the processing of an incoming requests loops somewhere but I cannot > find where exactly this happens (might be somewhere in StaxUtils ... but not > sure). > > I tried to replace a namespace in the soap header element but even if I use > the same value as replacement it hangs ...
I think the problem could be to do with the fact SOAP headers and body are produced as different documents, thus having this feature managing multiple outputs is causing a problem, even though it may not be dealing with the soap:Body. Perhaps we'd need to introduce a 'scope' property, ex, scope="soap:Envelope/soap:Header" or scope="soap:Envelope/soap:Body", or just "soapHeaders"/"soapBody" ? Not sure yet how to handle it, but may be SOAP interceptors dealing with headers/body can set the scope message property. Next we will have two features configured, once handling headers and one - body. Cheers. Sergey > > I've created a small sample project that can be used to reproduce the > problem. > > Regards, > Andi http://cxf.547215.n5.nabble.com/file/n4599185/cxf-sample.zip > cxf-sample.zip > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/Problem-with-new-transform-feature-tp4599185p4599185.html > Sent from the cxf-user mailing list archive at Nabble.com. > -- Sergey Beryozkin http://sberyozkin.blogspot.com Talend - http://www.talend.com
