Specifications

301ADOBE FLEX 3
Building and Deploying Adobe Flex 3 Applications
• Write a wrapper for the SWF file if you access it from an HTML, JSP, ASP, or another type of page.
A deployed SWF file can encompass your entire web application, however it is often used as a part of the appli-
cation. Therefore, users do not typically request the SWF file directly, but request a web page that references
the SWF file. Flex Builder can generate the wrapper for you, or, you can write the wrapper. For more infor-
mation, see “Creating a Wrapper” on page 311.
• Create a crossdomain.xml file on the server for data service, if you directly access any data services outside of
the domain that serves the SWF file. For more information, see
“Accessing data services from a deployed appli-
cation” on page 302
Deploying RSLs with Flex SDK
When your application uses an RSL, you must make sure to deploy the RSL on your deployment server, in the
same domain, unless you are using cross-domain RSLs. You use the
runtime-shared-libraries option of the
Flex compiler to specify the directory location of the RSL at compile time. Ensure that you copy the RSL to the
same directory that you specified with
runtime-shared-libraries. For more information, see “Using Runtime
Shared Libraries” on page 195.
Deploying modules with Flex SDK
Modules are SWF files that can be loaded and unloaded by an application. They cannot be run independently of
an application, but any number of applications can share the modules. When your application uses a module, you
must make sure to deploy the module’s SWF file on your deployment server in the same directory structure as you
used for your development environment. For more information, see “Creating Modular Applications” on
page 981 in the Adobe Flex 3 Developer Guide.
Deploying additional Flex files
The implementation of some Flex features requires that you deploy additional files along with your application’s
SWF file. For example, if you use deep linking functionality in your application, you must deploy the history-
Frame.html, history.css, and history.js files along with your application’s SWF file. If you use express install version
detection feature, you also must deploy the playerProductInstall.swf file with your SWF file. You typically deploy
these files in the same directory as your application’s SWF file.
For a complete list of additional Flex files that you might deploy with your application, see “Deployment checklist”
on page 304.