Web Services from a ColdFusion Server
When the server environment for web services is ColdFusion MX, you don’t have to do anything on the server side to consume a web service. The Flash movie merely has to reference the Flash Remoting adapter on the server. The ColdFusion MX Server contains the necessary SOAP translation requirements and creates a proxy for the web service. The Flash Remoting gateway translates the SOAP reply from the proxy into the ActionScript objects that Flash will understand.
Warning
As of ColdFusion Updater 3, web services are not enabled by default in ColdFusion MX. This is for security reason; a malicious user can hijack a Flash Remoting gateway to call web services. To enable the web services, the web.xml file in the ColdFusion MX installation needs to be changed. Read the Updater 3 release notes at http://www.macromedia.com/support/coldfusion/releasenotes/mx/releasenotes_mx_updater01.html for more information.
ColdFusion MX creates Java stub classes as a proxy for the web
service behind the scenes. These proxy classes are located in
ColdFusion_MX_root
\stubs.
Upon first calling the web service, the proxy is created. It remains
in place for subsequent calls. For that reason, the first call to the
service will take more time. The same is true for a web service
called through Flash Remoting using ASP.NET.
To demonstrate a simple example, we’ll call the Whois web service at http://www.soapclient.com/xml/SQLDataSoap.wsdl. Services such as these can be found at ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access