Thanks Zoran, We tried implementing the changes as suggested by you. But seems like they are not working for us.
Can you let me know how we could determine if we are using JAXB in our application. Can you also please tell how we could add NamespaceConfigurer to our application context registry via our implementation of SpringCameContext. Currently we have created a NamespaceConfigurer as below public class NamespaceConfigurer implements CxfEndpointConfigurer { private static final Logger LOGGER = LoggerFactory.getLogger(NamespaceConfigurer.class); @Override public void configure(final AbstractWSDLBasedEndpointFactory factoryBean) { LOGGER.debug("In NamespaceConfigurer.configure"); final JAXBDataBinding jaxb = new JAXBDataBinding(); final Map<String, String> namespacePrefixes = new HashMap<>(); namespacePrefixes.put("https://services.renewals.co.uk/", "ser"); jaxb.setNamespaceMap(namespacePrefixes); factoryBean.setDataBinding(jaxb); } } Then created a bean in our CamelConfig class as below @Bean(name="apadcRemoteNamespaceConfigurer") public NamespaceConfigurer apadcRemoteNamespaceConfigurer() { return new NamespaceConfigurer(); } And then tried calling this in target URI as below String uri = "cxf://" + url + "?wsdlURL=" + wsdlUrl + "" + "&synchronous=true" + "&dataFormat=" + dataFormat.name() + "&loggingFeatureEnabled=true"; if (dataFormat == DataFormat.PAYLOAD) { uri = uri + "&defaultOperationName=" + operationName; } uri = uri + "&cxfEndpointConfigurer=#apadcRemoteNamespaceConfigurer"; Please can you help us with the correct approach to create this functionality. -- 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-tp5789743p5789897.html Sent from the Camel Development mailing list archive at Nabble.com.