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

134 Chapter 7: Using Flash Remoting for Java
}
public String getServletInfo()
{
return "A test servlet.";
}
public ServletConfig getServletConfig()
{
return null;
}
public void destroy()
{
message = null;
}
}
To handle the function results in ActionScript, you use a result handler function like this one:
function MyServlet_Result (result:mx.rpc.ResultEvent):Void
{
ResultBox.text = result.result;
}
For more information, see “Handling function results in ActionScript” on page 137.
Calling JMX MBeans from Flash (JRun only)
You can call Macromedia JRun application functionality through JMX using Flash Remoting.
You connect to a JMX MBean object using the MBean object name in the ActionScript
Service() constructor. Service functions are methods defined in the MBean’s manageable
interface. The following sections describe how to get a reference to a JMX MBean object and call
its methods.
To grant clients access to JMX MBeans, you must provide permissions that specify the exposed
MBean object names in the jrun_root/lib/jrun.policy file. For example, the following line of text,
which is currently uncommented in the jrun.policy file, exposes
DeployerService for the JRun
Flash samples:
permission jrun.security.JMXPermission
"accessMBean.DefaultDomain:service=DeployerService";
You can also use wildcards to grant access to JMX MBeans. For example, to grant access to all
MBeans under the default domain using a wildcard, you would uncomment the following line in
the jrun.policy file:
// permission jrun.security.JMXPermission "accessMBean.DefaultDomain:*";