Have a look at Transformation Feature:
http://cxf.apache.org/docs/transformationfeature.html
setting an inTransformElements property to have
doFspQueryInfo: {http://fsp.site.com}doFspQueryInfo
should do it
Sergey
On 14/07/12 18:50, rimling wrote:
I have endpoint on CXF (standalone app using jetty), generated from third
party WSDL. In WSDL used RPC/literal binding. Client, which based on CXF
correctly work. But Axis-client of our partner receive fault "Message part
doFspQueryInfo was not recognized". doFspQueryInfo is operation.
Request, generated by CXF has namespace:
<soap:Body>
<ns1:doFspQueryInfo xmlns:ns1="http://fsp.site.com";>
<FspQueryReq>
<messageID>msgid-10</messageID>
</FspQueryReq>
</ns1:doFspQueryInfo>
</soap:Body>
Axis request looks similar, but without namespace:
<soap:Body>
<doFspQueryInfo xmlns="">
<FspQueryReq>
<messageID>msgid-10</messageID>
</FspQueryReq>
</doFspQueryInfo>
</soap:Body>
So, question, can I force CXF to understood request from Axis?
Answer was searched in this list and in internet several days, but without
success.
--
View this message in context:
http://cxf.547215.n5.nabble.com/RPC-Literal-Axis-vs-Cxf-and-namespace-tp5711079.html
Sent from the cxf-user mailing list archive at Nabble.com.
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Blog: http://sberyozkin.blogspot.com
