The other option is if you configure in a property of: "soap.env.ns.map"
which is a map of prefix -> ns and then also add the property of: "disable.outputstream.optimization", "true" then you can have fairly complete control over the prefixes that are used and have them output on the SOAP:Envelope. Dan On Tuesday, April 17, 2012 05:00:57 PM Arthur van Dorp wrote: > Hi all > > I am trying to switch a webservice client over from Axis2 to CXF 2.5.2 > with JAXB for databinding. > > The server it is talking to is implemented with Axis2. Whenever I use the > CXF client, the Axis2 server ignores some parts of the request. It looks > exactly like the problem described in the question over at stackoverflow: > > http://stackoverflow.com/questions/9537462/cxf-codegen-generated-client-ne > eds-namespace-on-the-soap-envelope/ > > The request the Axis2 client generates has a namespace prefix for every > element whereas the CXF/JAXB generated code uses a default namespace and > omits the prefix. Nothing wrong with that in my book, but it doesn't seem > to work with the Axis2 server. > > Using XMLBEANS for databinding works, but has other downsides. I would > like to use JAXB. > > Any ideas on how to resolve this problem on the CXF client side (even if > it might be an Axis2 bug)? > > Thanks and regards > > Arthur -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
