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
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