Re: how to change default namespace ns1 or ns2 added by Camel to custom namespace

[sandesh.naik]

Thanks for replying Zoran

I now think we have the NamespaceConfigurer registered as I can see a debug
message from the configure method appear at app startup and it is also
changing the behaviour of the web service call.

However, in terms of the changed behaviour, not only is the 'ns1' namespace
prefix still not being replaced with 'ser' but the payload of the web
service call appears to be being encoded/encrypted, i.e. -

...
<soap:Body>
    <ns1:quote xmlns:ns1=&quot;https://&lt;domain>/">
        <Request>PD94bWwgdmVyc2lvb
        ...
        AgICAgICAgICA8L1BvbXNSZXF1ZXN0Pg==</Request>
    </ns1:quote>
</soap:Body>
...

Is there some config of CxfEndpointConfigurer/JAXBDataBinding that I need to
specify to stop this?

Also, does CxfEndpointConfigurer/JAXBDataBinding honour the config already
specified in the 'cxf://...' URI?

Thanks again




--
View this message in context: 
http://camel.465427.n5.nabble.com/how-to-change-default-namespace-ns1-or-ns2-added-by-Camel-to-custom-namespace-tp5789743p5789956.html
Sent from the Camel Development mailing list archive at Nabble.com.