Specifications

223ADOBE FLEX 3

Building and Deploying Adobe Flex 3 Applications

In the Deployment Path/URL field, enter the location of the SWZ file. For example, “http://www.remote-

server.com/rsls/framework_3.0.183453.swc”. The application tries to load the RSL from this location at run

time. The location can be relative to the application’s SWF file, or a full URL to a remote server. If the RSL is

on a remote server, you might also be required to point to the policy file. In the Policy file URL field, enter the

location of the crossdomain.xml file, if there is no crossdomain.xml file at the target server’s root. You do not

need to enter anything in this field if the application’s SWF file and the RSLs are served from the same domain,

or if the crossdomain.xml file is at the target server’s root.

4 Click OK to save your changes in the Edit RSL Deployment Path dialog box.

5 Repeat the previous two steps for the SWF file, if you are also deploying the unsigned framework RSL with

your application. If you do not deploy the failover SWF file, then users with Flash Player versions earlier than

9.0.115 will not be able to use your application.

6 Click OK to save your changes to the Library Path Item Options dialog box.

7 Ensure that the Verify RSL Digests option on the Library Path tab is selected.

8 Click OK to save your changes to the Flex Build Path settings.

When you deploy your application, you must manually copy the framework RSLs to the path that you specified

on the remote server.

Using the framework RSLs on the command line

The following example application shows how to use the framework RSLs on the command line.

You first create an application that uses at least one visual Flex component. For example, the following application

uses a Button control:

<?xml version="1.0"?>

<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml">

<mx:Button label="Submit"/>

</mx:Application>

Save this file as SimpleApp.mxml and store it in the project/src directory.

After you create the application, determine the size of the application’s compiled SWF file before you use the

framework RSL. This will give you an idea of how much memory you are saving by using the framework RSL.

Compile this application as you normally would, with one exception. Add the

static-link-runtime-shared-

libraries=true

option; this ensures that you are not using the framework RSL when compiling the application,

regardless of the settings in your configuration files. Instead, you are compiling the framework classes into your

SWF file.