Messages
Reply
Edit
Delete
Don't know. I'd have to look at the service to import it to see what's happening.
The soap namespace is there, so that should work...
+++ Rick ---
From what I can determine, it does appear to be setup as a Soap service... the wsdl page shows this as the header:
This XML file does not appear to have any style information associated with it. The document tree is shown below.
<definitions xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="urn:TroxAPI" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="urn:TroxAPI">
<types>
<xsd:schema targetNamespace="urn:TroxAPI">
<xsd:import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
<xsd:import namespace="http://schemas.xmlsoap.org/wsdl/"/>
</xsd:schema>
</types>
You sure the service is a Soap 1.x service and not a WS* service?
In many cases WS* services will import but not work due to the WS* protocol extensions that are not supported by the proxy client (ie. none of the ws* values are fed to the service).
+++ Rick ---
I am getting this error from one of our Web Services...
“Namespace prefix 'soap' not defined..”
“Generate” is successful, but the error above occurs when attempting to make a call to the Web Service.
West Wind Technologies
Making waves on the Web
