Specifications
225ADOBE FLEX 3
Building and Deploying Adobe Flex 3 Applications
Troubleshooting RSLs
RSLs can be complicated to create, use, and deploy. The following table describes common errors and techniques
to resolve them:
Error Resolution
#1001
This error indicates that the digest of a library does not match the RSL SWF file. When you compile an appli-
cation that uses an RSL, you specify the library SWC file that the application uses for link checking at compile
time and an RSL SWF file that the application loads at run time. The digest in the library’s catalog.xml file
must match the digest of the RSL SWF file or you will get this error. If this error persists, recompile the appli-
cation against the library SWC file again and redeploy the application’s SWF file.
If you are using framework RSLs, then the SWZ file is a different version than what the application was
compiled against. Check whether this is the case by adding a failover RSL SWF file and recompiling. If the
error does not recur, then the SWZ file is out of sync.
#2032
This error indicates that the SWZ or SWF file is not being found.
For example, if you specified only “mylib.swf” as the value of the
rsl-url parameter to the runtime-
shared-library-path
option, but the SWF file is actually in a sub-directory such as /rsls, then you must
either recompile your application and update the value of the
rsl-url parameter to “rsls/mylib.swf”, or
move mylib.swf to the same directory as the application’s SWF file.
#2046
This error indicates that the loaded RSL was not signed properly. In the case of framework RSLs, the frame-
work’s SWZ file that the application attempted to load at run time was not a properly signed SWZ file. You
must ensure that you deploy an Adobe-signed RSL.
#2048
The cause of this error is that you do not have a crossdomain.xml file on the server that is returning the RSL.
You should add a file to that server. For more information, see “Using cross-domain policy files” on page 40.
If you put the crossdomain.xml file at the server’s root, you do not have to recompile your Flex application.
This is because the application will look for that file at the server’s root by default, so there is no need to
explicitly define its location.
If you cannot store a crossdomain.xml file at the remote server’s root, but can put it in another location on
that server, you must specify the file’s location when you compile the application. On the command line, you
do this by setting the value of the
policy-file-url argument of the runtime-shared-library-path
option.
In the following example, the RSL SWF file is located in the /rsls directory on www.domain.com. The cross-
domain.xml file is located in the same directory, which is not the server’s root, so it must therefore be explic-
itly specified:
mxmlc -runtime-shared-library-path=
../lib/mylib.swc,
http://www.mydomain.com/rsls/myrsl.swf,
http://www.mydomain.com/rsls/crossdomain.xml
Main.mxml