In my case I don't think I need to transform the namespace but rather it's being generated incorrectly by the server when it hosts the service. Perhaps I'm got doing things incorrect for 'WSDL First' approach. I'm using the Maven plugin's wsdl2java goal to generate the java code (for client and server) but I need CXF to retain the original WSDL when it hosts the service. Is there an example of this someplace?
-Dave On Tue, Apr 29, 2014 at 11:35 PM, Jose María Zaragoza <[email protected]>wrote: > Hello: > > You can have a look at > > https://cxf.apache.org/docs/transformationfeature.html > > Maybe it'ts not what you want, but it cold fix it > > Regards > > > 2014-04-30 6:15 GMT+02:00 David Hoffer <[email protected]>: > > I'm getting the following exception calling a CXF hosed (WSDL first) > > webservice with a CXF client. The namespace should be > > http://soap.sforce.com/2005/09/outbound but is http://outbound._09._ > > 2005.soap.sforce.com instead. > > > > javax.xml.ws.soap.SOAPFaultException: Unexpected wrapper element { > > http://outbound._09._2005.soap.sforce.com/}notificationsResponse found. > > Expected {http://soap.sforce.com/2005/09/outbound}notificationsResponse. > > > > This seems to be happening because on the server when the code is > generated > > from the WSDL, since the folders start with numbers underscores are > added. > > Then when the server builds the service it seems to ignore the following > > specification of the namespace: > > > > @WebService(targetNamespace = "http://soap.sforce.com/2005/09/outbound";, > > name = "NotificationPort") > > > > Instead it builds a new WSDL/namespace based on the package names there > > were changed to handle the digits. So it changes it to http://outbound. > > _09._2005.soap.sforce.com/ > > > > How can I keep the original namespace and ignore what package names are > > used? > > > > -Dave >
