Assuming the server's SWFFolder contains the application, I don't see any reason by linking with RSLs would cause a problem. After linking with RSLs your application swf will be different from the "merged into code" one, so the new application will need to be copied to the SWFFolder. Are you waiting for 5 mins (or whatever your UpdateInterval is) after copying the application swf to the server? Do you see any errors logged by the server?
yes. every time i compile new application i copy it to the server, and wait several minutes , the application with merged linkage works, and the one with default framework linkage (rsl) doesn't
1 person found this helpful
Do you copy all of the *.swz and *.swf files from /frameworks/rsls to the SWFFolder?
If you still don't have any luck, then please write up a bug report.
Here are a couple of guesses to try to work around the problem if copying the RSLs did not work.
1. Each library (swc) has RSL URLs. Switch the order of the existing RSL URLs so the primary RSL is loaded from the same directory as the application and the failover RSL URL comes from http://fpdownload.adobe.com. If the RSL is being verified instead of the application then this may help it being found in the SWFFolder.
2. Link your application with RSL linkage but change the settings for spark.swc and osmf.swc to "merged into code". If RSLs are causing the problem then this may workaround it but still allow you to use some RSLs.
thank you Darrell
Could this just be an issues that app is taking too long to load etc and the swf verification is timing out (you see under 3.5 timing tags?). I am seeing this issues on group of my boxes but if I pull my box out of the group and go directly at it it works.