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
Configuring Flash Remoting 39
Note: If you specify the Flash Remoting gateway in the web page, the ActionScript import mx.
remoting.Service;
directive must be on the Flash Timeline, not in a SWF file.
When you specify the gateway connection in a Web page, you specify the gatewayUrl parameter
as an empty string in the Service constructor that you create to access the service. For example, the
following HTML
flashvars parameter creates the gateway connection and the subsequent
Service parameter, which accesses the
customerData service, submits an empty string for the
gatewayUrl parameter.
<param name="flashvars" value="gatewayUrl=http://localhost:8300/flashservices/
gateway/"/>
// Service constructor
custService = new Service(
"", // set using flashvars to http://localhost:8300/flashservices/
null,
"customerData",
null,
null);
Specifying a service
The service name format depends on the type of service you are using. The following table lists
the ways that you can specify service names for the supported service types:
Service type Service name Example
Web services (accessed
through ColdFusion or .NET
servers)
URL of the WSDL file for the
service.
http://www.xmethods.net/sd/
2001/BabelFishService.wsdl
ASP.NET pages (.aspx) Logical directory path from the web
root. Replace all slash or backslash
characters in the path with periods.
FlashGateway.Samples.
WeatherService
DLL files (.dll) Fully qualified class name. Flashgateway.Samples.
WeatherService
EJBs JNDI name of the EJBHome
binding.
com.mycompany.samples.
WeatherService
Java classes, including
JavaBeans
Fully qualified Java class name. com.mycompany.samples.
WeatherService
Java servlets Web application context root. WeatherService
JMX (JRun 4 only) MBean object name. DefaultDomain:service=
DeployerService
ColdFusion pages (.cfm) Path from the web root to the page’s
directory. Replace all forward slash
or backward slash characters in the
path with periods.
Flashgateway.samples.
WeatherService
ColdFusion components (.cfc) Qualified ColdFusion component
name starting from the web root.
Flashgateway.samples.
WeatherService