Specifications

305ADOBE FLEX 3
Building and Deploying Adobe Flex 3 Applications
History management and deep linking To support history management and deep linking, you must include the following files in your
deployment:
• history.js
• history.css
• historyFrame.html
You must import the first two files into your HTML wrapper, and store all through of these files
in a /history subdirectory.
For more information, see “Deep Linking” on page 1065 in the Adobe Flex 3 Developer Guide.
Runtime shared libraries (RSLs) For standard RSLs, deploy the RSL SWF files with your Flex application. You must be sure to
deploy the SWF files to the same relative location that the compiler used. If you are deploying
an a custom RSL, be sure to optimize the RSL’s SWF file prior to deployment.
For framework RSLs, be sure to deploy both the signed (*.SWZ) and unsigned (*.SWF) RSLs.
For framework and cross-domain RSLs, be sure to deploy failover RSLs to the locations you
specified when you compiled the application.
For more information, see “Using Runtime Shared Libraries” on page 195.
Runtime stylesheets If you use runtime stylesheets in your application, you must deploy the SWF files so that they
can be loaded. You can load run-time stylesheet SWF files either locally or remotely. However,
if you load them locally, the stylesheets must be in the same relative location that you specified
in the application.
For more information, see “Loading style sheets at run time” on page 633 in the Adobe Flex 3
Developer Guide.
Modules If your application uses modules, you must deploy the module SWF files so that they can be
loaded.
Modules are SWF files that can be loaded and used by any number of applications. If multiple
applications use your modules, then you should deploy them to a location that all applications
can load them from rather than deploy them multiple times across different domains.
For more information, see “Creating Modular Applications” on page 981 in the Adobe Flex 3
Developer Guide.
Runtime localization If your application uses run-time localization (if it, for example, lets the user switch from English
to Japanese language at run time), then you might need to deploy resource module SWF files.
These modules can contain one or more resources bundles for one or more locales.
For more information, see “Localizing Flex Applications” on page 1101 in the Adobe Flex 3
Developer Guide.
Feature Assets to Deploy