1 person found this helpful
This is because when you run in FB, the output folder is automatically part of the trust and hence it works. Ideally it should work, if you deploy it on a webserver but since you tried it on a different untrusted location it is failing. You can either put that location in the trust location (look for FlashPlayerTrust directory in your users folder and edit the .cfg file there to include your location) or the recommended approach is to deploy it on a webserver and provide appropriate crossdomain.xml file as a security measure (more info http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf69084-7ec8.html )
Thank you for directions about Adobe FB development vs deployment. Here are a couple follow-up questions:
Background: FB application developers download an Adobe Flash 32-bit debugger version to a Windows 7 64-bit PC.
1) So far, the Flash debugger does not co-exist with a Flash runtime version; each requires removing the other before installation. Hence, developer PCs do not have both Flash versions.
2) When using FB4 and Flash debugger, this security folder is created.
but no other FlashPlayerTrust folder is created.
The FlashPlayerTrust folder contains:
air.1.0.trust.cfg // adding the program name.html does not help, adding PC IP address does not help
flashbuilder.cfg // contains paths to metadata and other files, adding program name does not help
flashbuilder.fbr // contains plugins, etc.
What is the correct file, program or IP address syntax? Does the PC need rebooting after editing the file?
3) Documentation for deploying to a server and editing crossdomain.xml file looks complete
Any help from Adobe????
Did you get the answer for your issue. I have similar one eventhou I deployed to webserver.
we already have the webservice utilised via WSDL why bother create new one.. please anyone???
You will need to use a crossdomain file and put it in your apache root documents directory for that server/port.
That should resolve your security issues.