-
1. Re: Web Services without WSDL
Hi,
What happens when you suffix a '?wsdl' term with your webservice url?... -
2. Re: Web Services without WSDL
Whether I type http://example.com/core.php or http://example.com/core.php?wsdl - I get the following:
<SOAP-ENV:Envelope SOAP-ENV:encodingStyle=" http://schemas.xmlsoap.org/soap/encoding/">
−
<SOAP-ENV:Body>
−
<SOAP-ENV:Fault>
<faultcode xsi:type="xsd:string">Client</faultcode>
<faultactor xsi:type="xsd:string"/>
<faultstring xsi:type="xsd:string">method '' not defined in service</faultstring>
<detail xsi:type="xsd:string"/>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
If I try using cfinvoke I get a "Unable to read WSDL from URL" 500 internal server error.
BTW this is my first day learn CF ;)
Thanks -
3. Re: Web Services without WSDL
You might try using CFHTTP.
http://www.jamesnetherton.com/blog/index.cfm/2007/1/14/Invoking-a-webservice-using-CFHTTP -
-
5. Re: Web Services without WSDL
Thanks so much for your quick responses!! Using that CFHTTP example - I am now getting the expected response.
Cheers. -
6. Re: Web Services without WSDL
quote:
Originally posted by: logic8
Whether I type http://example.com/core.php or http://example.com/core.php?wsdl - I get the following:
<SOAP-ENV:Envelope SOAP-ENV:encodingStyle=" http://schemas.xmlsoap.org/soap/encoding/">
−
<SOAP-ENV:Body>
−
<SOAP-ENV:Fault>
<faultcode xsi:type="xsd:string">Client</faultcode>
<faultactor xsi:type="xsd:string"/>
<faultstring xsi:type="xsd:string">method '' not defined in service</faultstring>
<detail xsi:type="xsd:string"/>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
If I try using cfinvoke I get a "Unable to read WSDL from URL" 500 internal server error.
BTW this is my first day learn CF ;)
Thanks
Never too early to start good habits, such as reading your error messages. What do you think this means?
<faultstring xsi:type="xsd:string">method '' not defined in service</faultstring>