Thanks for your reply!
To provide some more info on the error:
The error occurs even in Tomcat environment on local machine. The application works fine if you execute it directly v/s from a web server.
So, the following would work just fine:
And the following would not:
I have experienced that keeping up with nightly build comes with itsown challenges and so haven't dared change since build 12222.For example, with one of the earlier nightly build, I had to upgrade my VideoPlayer and since it has changed so much, my application's video player is still broken! I have posted for help on this forum but with no reply. </sob story>
It looks like, I may not have any options here. I'll update this discussion with my finding after the upgrade to the latest nightly build.
I'm updating to build 12891 and I see that there have been very significant changes in namspaces. Before I attempt to fix (literally) hundreds of errors due to namespace changes on classes such as mx:Image, mx:State, mx:Spacer, etc, I would like to know if these changes and new name spaces (ns, ns1, etc) are somewhat final? Do you know? Any guidance is highly appreciated.
After upgrading to build 12891, the application works.
As always, I really appreciate your help.
After one of the recent Flex 4 SDK build, the application has started depending on additional files such as osmf_4.0.0.xxxxx.swf, where xxxxx is the build number. These files are generated by Flash Builder upon compilation and should be saved where you copy your application's own swf file on the web server serving your application.
In my case, updating application to build 12891 and making sure these additional files are appropriately copied solved the problem.
The OSMF issue is likely something on our end with RSLs not being copied to the server correctly.
We're investigating the issue.