Hi,
I think if you simply pass the request through a CXF transformation
feature then a prefix will be added, ex, set an outTransformElements
property like this:
{http://myns}* : {http://myns}*
There could be a much simpler option for the JAX-WS fronthend, but I'm
not aware of it
I haven't tried but my work. The default namespace can also be
enforced with the feature of needed
HTH
Sergey
On Tue, Apr 17, 2012 at 4:00 PM, Arthur van Dorp <[email protected]> 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-needs-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
>
>
> --
> Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
> belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
--
Sergey Beryozkin
http://sberyozkin.blogspot.com
Talend - http://www.talend.com
