User Guide
Table Of Contents
- Contents
- About Flash Remoting
- Getting Started
- Using Flash Remoting ActionScript
- Using the RemotingConnector component (Flash Professional only)
- Using Flash Remoting Data in ActionScript
- About Flash Remoting and data types
- Understanding Action Message Format
- Converting from ActionScript to application server data types
- Converting from application server data types to ActionScript
- ColdFusion to ActionScript data conversion issues
- About working with objects
- About working with RecordSet objects
- About working with XML
- The NetConnection Debugger
- Using Flash Remoting with ColdFusion MX
- Using Flash Remoting for Java
- About Flash Remoting for Java
- Calling Java classes or JavaBeans from ActionScript
- Calling Enterprise JavaBeans (EJBs) from Flash
- Calling servlets and JSPs from Flash
- Calling JMX MBeans from Flash (JRun only)
- Calling server-side ActionScript from Flash (JRun only)
- Handling function results in ActionScript
- Using Flash Remoting with JRun security
- Passing XML objects between Flash and Java
- Viewing Flash Remoting log entries
- Using Flash Remoting for Microsoft .NET
- Flash Remoting for Microsoft .NET
- Calling ASP.NET pages from Flash
- Making an ASP.NET page available to Flash Remoting
- Getting a reference to an ASPX-based service in ActionScript
- Invoking ASPX pages in ActionScript
- Using the Flash Remoting custom server control in ASPX pages
- Using the Flash Remoting namespace in code-behind files
- Using ASP.NET state management with Flash Remoting
- Using ASP.NET exception handling
- Using ADO.NET objects with Flash Remoting
- Displaying a RecordSet object in Flash with ActionScript
- Calling web services from Flash
- Calling ASP.NET assemblies from Flash
- Viewing Flash Remoting log entries
- Using NetServices and Connection Classes
- Index

Using Flash Remoting with ColdFusion components 109
</cffunction ...>
</cfcomponent>
You can also pass arrays, structures, and named objects using this syntax. The following
ActionScript code defines an object:
var params:Object = new Object();
params.first = "Hello";
params.second = true;
service.concat(params);
In a component, you access the object elements using named parameters, as follows:
<cfcomponent>
<cffunction name="concat" access="remote" returntype="any">
<cfargument name="first" type="any" required="true">
<cfargument name="second" type="any" required="true">
<cfreturn first & second>
</cffunction>
</cfcomponent>
This component specifies that two parameters are required. An ActionScript object satisfies this
requirement, because it is split into named arguments. However, an ActionScript array does not.
Passing objects from ActionScript lets you use the Arguments scope within a component
function. The Arguments scope works the same way as the Flash scope in ColdFusion pages. In a
component, you can access parameters using the syntax
Arguments.paramName. Therefore, you
can access the params object from the previous example as follows:
<cfcomponent>
<cffunction name="concat" access="remote" returntype="any">
<cfset p1=Arguments.first>
<cfset p2=Arguments.second>
</cffunction>
</cfcomponent>
Using component metadata with the Flash Remoting service
Flash designers can use the Service Browser in the Flash authoring environment to discover
business logic functionality built into ColdFusion. You use the
description attribute of the
cffunction and cfargument tags to describe the ColdFusion functionality to the Service
Browser.