This is how I'm calling it:
----------------------------
<cfinvoke
webservice="
http://xxxxxxx.com/_xxxxxxx.cfc?wsdl"
method="getFTPInfo"
returnvariable="xxx">
<cfinvokeargument name="userName" value="xxxxx">
<cfinvokeargument name="userPassword" value="xxxxx">
</cfinvoke>
<cfdump var="#xmlParse(xxx)#" label="getFTPInfo">
<cfcatch type="Any">
<h1>Error</h1>
<cfdump var="#cfcatch#">
</cfcatch>
</cftry>
----------------------------
The error is thrown by the first CFDUMP. Here's the "Detail"
at the top of the caught dump:
----------------------------
Name:
http://xxxxxx.com/_xxxxxxxxxx.cfc?wsdl.
WSDL:
http://xxxxxxx.com/_xxxxxxxxxxxx.cfc?wsdl.
org.xml.sax.SAXException: Fatal Error: URI=null Line=2: The
document type declaration for root element type "html" must end
with '>'. It is recommended that you use a web browser to
retrieve and examine the requested WSDL document for correctness.
If the requested WSDL document can't be retrieved or it is
dynamically generated, it is likely that the target web service has
programming errors.
----------------------------
When I look at the _xxxxxxxxxx.cfc?wsdl as suggested, in the
browser, it loads fine. No hassles.
If I call the method via componant, thusly:
----------------------------
<cftry>
<cfinvoke
component="_xxxxxxxxx"
method="getFTPInfo"
returnvariable="xxx">
<cfinvokeargument name="userName" value="xxxxxx">
<cfinvokeargument name="userPassword" value="xxxxxx">
</cfinvoke>
<cfdump var="#xmlParse(xxx)#" label="getFTPInfo">
<cfcatch type="Any">
<h1>Error</h1>
<cfdump var="#cfcatch#">
</cfcatch>
</cftry>
----------------------------
It works fine, no errors.
As mentioned above, this exact service works on other domains
(all running the same code base on the same server, just coming in
via different domains and calling data from different dbs)
My first thought was that the info being sent back may have
some illegal characters, but that's not the case. See code snippet
below to see the kind of data that is being sent back.
Abinidi I did clear the /stubs folder and no change. Also
went into the Administrator and saw that this ws hadn't yet been
registered there.