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

Calling Enterprise JavaBeans (EJBs) from Flash 129
mx.remoting.debug.NetDebug.initialize();
//…
function runExample()
{
var SampleLoanHome:Service = new Service(
"http://localhost:8300/flashservices/gateway",
null,
"SampleLoanEjbHome",
null,
null);
var pc:PendingCall = SampleLoanHome.create();
pc.responder = new RelayResponder(this, "create_Result", "create_Fault");
}
function create_Result( re:ResultEvent )
{
flashStatelessEJB = re.result;
calculate();
}
function create_Fault( fe:FaultEvent )
{
mx.remoting.debug.NetDebug.trace({level:"None", message:"There was a
problem" + fe.fault.faultstring});
}
function calculate()
{
var cal_pc:PendingCall = flashStatelessEJB.calculate( (number
(principalInput.text)), (number (monthsInput.text)), (number
(rateInput.text)) );
cal_pc.responder = new RelayResponder(this, "calculate_Result",
"calculate_Fault");
}
To handle the function results, you use a result handler function like the following:
function calculate_Result (re:ResultEvent)
{
payOutput.text = re.result;
}
function calculate_Fault( fe:FaultEvent )
{
mx.remoting.debug.NetDebug.trace({level:"None", message:"There was a
problem" + fe.fault.faultstring});
}
For more information, see “Handling function results in ActionScript” on page 137.
Looking at a Flash application that calls an EJB
The following sections illustrate the three pieces required to call an EJB from Flash Remoting:
• “Looking at the EJB code” on page 130
• “Looking at the user interface for the EJB” on page 130
• “Looking at the ActionScript code that calls the EJB” on page 131