Consuming web services
717
Consuming web services that are not generated by ColdFusion MX
To consume a web service that is implemented in a technology other than ColdFusion MX, the
web service must have one of the following sets of options:
•
rpc as the SOAP binding style and encoding as the encodingStyle
•
document as the SOAP binding style and literal as the encodingStyle
The following example shows a portion of the WSDL file for the BabelFish web service:
<binding name="BabelFishBinding" type="tns:BabelFishPortType">
<soap:binding style="rpc"
transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="BabelFish">
<soap:operation soapAction="urn:xmethodsBabelFish#BabelFish" />
<input>
<soap:body use="encoded" namespace="urn:xmethodsBabelFish"
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</input>
<output>
<soap:body use="encoded" namespace="urn:xmethodsBabelFish"
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</output>
</operation>
</binding>
The WSDL file for the BabelFish web service is compatible with ColdFusion MX because it uses
rpc as the binding style and encoding as the encodingStyle.
Calling web services from a Flash client
The Flash Remoting service lets you call ColdFusion pages from a Flash client, but it does not let
you call web services directly. To call web services from a Flash client, you can use Flash Remoting
to call a ColdFusion component that calls the web service. The Flash client can pass input
parameters to the component, and the component can return to the Flash client any data
returned by the web service.
For more information, see
Chapter 29, “Using the Flash Remoting Service,” on page 641
.
Catching errors when consuming web services
Web services might throw errors, including SOAP faults, during processing that you can catch in
your application. If uncaught, these errors propagate to the browser.
To catch errors, you specify an error type of application to the ColdFusion
cfcatch
tag, as the
following example shows:
<cftry>
Put your application code here ...
<cfcatch type="application">
<!--- Add exception processing code here ... --->
</cfcatch>
...
<cfcatch type="Any">
<!--- Add exception processing code appropriate for all other
exceptions here ... --->
</cfcatch>
</cftry>
For more information on error handling, see
Chapter 14, “Handling Errors,” on page 285
.
Summary of Contents for COLDFUSION MX 61-DEVELOPING COLDFUSION MX
Page 1: ...Developing ColdFusion MX Applications...
Page 22: ...22 Contents...
Page 38: ......
Page 52: ...52 Chapter 2 Elements of CFML...
Page 162: ......
Page 218: ...218 Chapter 10 Writing and Calling User Defined Functions...
Page 250: ...250 Chapter 11 Building and Using ColdFusion Components...
Page 264: ...264 Chapter 12 Building Custom CFXAPI Tags...
Page 266: ......
Page 314: ...314 Chapter 14 Handling Errors...
Page 344: ...344 Chapter 15 Using Persistent Data and Locking...
Page 349: ...About user security 349...
Page 357: ...Security scenarios 357...
Page 370: ...370 Chapter 16 Securing Applications...
Page 388: ...388 Chapter 17 Developing Globalized Applications...
Page 408: ...408 Chapter 18 Debugging and Troubleshooting Applications...
Page 410: ......
Page 426: ...426 Chapter 19 Introduction to Databases and SQL...
Page 476: ...476 Chapter 22 Using Query of Queries...
Page 534: ...534 Chapter 24 Building a Search Interface...
Page 556: ...556 Chapter 25 Using Verity Search Expressions...
Page 558: ......
Page 582: ...582 Chapter 26 Retrieving and Formatting Data...
Page 668: ......
Page 734: ...734 Chapter 32 Using Web Services...
Page 760: ...760 Chapter 33 Integrating J2EE and Java Elements in CFML Applications...
Page 786: ...786 Chapter 34 Integrating COM and CORBA Objects in CFML Applications...
Page 788: ......