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

156 Chapter 8: Using Flash Remoting for Microsoft .NET
import mx.rpc.RelayResponder;
import mx.rpc.FaultEvent;
import mx.remoting.PendingCall;
// get a reference to the ASPX-based service
var ASPXservice:Service = new Service("http://localhost/myASPApp/
default.aspx",null,"myASPApp",null,null);
// call the ASPX page
var pc:PendingCall = ASPXservice.myASPPage();
pc.responder = new RelayResponder(this, "myASPPage_Result",
"myASPPage_Fault");
// handler for ASPX page results
function myASPPage_Result(re:ResultEvent):Void
{
DataGlue.bindFormatStrings(displayNames, re.result, "#SSN#","#ID#");
}
You can also use the DataGlue.BindFormatFunction function to create custom formatting for
your record sets. For more information on displaying record sets in ActionScript, see Chapter 4,
“Using Flash Remoting Data in ActionScript,” on page 63.
Calling web services from Flash
Using the Flash Remoting web service adapter, you can call web services from Flash that are
described by the Web Services Description Language (WSDL). You must first generate a local
web service proxy to interact with web services. After you create the proxy, the ActionScript in
your Flash application can then invoke web service methods through the proxy, which handles
sending and receiving Simple Object Access Protocol (SOAP) messages with the remote web
service.
In .NET, you can generate proxy assemblies with the WSDL Tool (wsdl.exe). Flash Remoting for
.NET also uses the WSDL Tool to generate SOAP proxies for web services automatically from
valid WSDL, either local or remote. In addition, Flash Remoting does not restrict you to
.NET-based web services. Rather, any WSDL-described web service is available to Flash
Remoting.
If you want to invoke web services using a .NET web service proxy assembly of your own that
contains the web service definition, place the DLL file into the local assembly cache of your
ASP.NET application. The proxy DLL must have exactly the same name as the web service, as
described by the WSDL’s service element. To invoke the web service proxy from ActionScript,
supply the web service’s fully qualified WSDL URL as the service address argument of the
Service constructor, and use the web service’s method names as the service function names.