|
Thanks for your reply- it is reason why there are double tags. I've done it that way because when there is useJBIWrapper="false" useSOAPEnvelope="false" in provider and consumer - the target of provider can't recognize the message - there are double tags in request. In second case : useJBIWrapper="false" useSOAPEnvelope="true"> I don't know why my xpath _expression_ doesn't work, there is a payload: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:heal="http://myservice/aaa"><soap:Body><heal:getCommunitiesRequest xmlns:heal="http://myservice/aaa"> <heal:dataSourceId>1</heal:dataSourceId> </heal:getCommunitiesRequest></soap:Body></soap:Envelope> org.apache.cxf.interceptor.Fault: Invalid xpath: local-name(/soap:Envelope/soap:Body/*[1])='getCommunitiesRequest'. Reason: javax.xml.xpath.XPathExpressionException but local-name(/soap:Envelope/soap:Body/*[1])='getCommunitiesRequest' I think is correct. In my wrong configuration with false,false for consumer and false,true for provider the payload was just <heal:getCommunitiesRequest xmlns:heal="http://myservice/aaa"> <heal:dataSourceId>1</heal:dataSourceId> </heal:getCommunitiesRequest> so the xpath was simpler : local-name(/*[1])='getCommunitiesRequest' and it worked... So what - am I doing something wrong with xpath? should I do something else with soap namespaces in serviecemix and camel? On 05.01.2012 14:26, Freeman Fang wrote: Hi, --
| ||||||||
Title: This email may contain confident
- double soap:Body and soap:envelope tags in cxf-bc response Rafal Janik
- Re: double soap:Body and soap:envelope tags in cxf-bc re... Freeman Fang
- Re: double soap:Body and soap:envelope tags in cxf-b... Rafal Janik
- Re: double soap:Body and soap:envelope tags in c... Rafal Janik
- Re: double soap:Body and soap:envelope tags ... Freeman Fang
