Copy link to clipboard
Copied
We have a large and complex extension written using as3 and JSFL.
Recently I’ve been having a go at trying to incorporate it into the extension builder in order to be able to debug it.
I have created a envelope application that loads out main application swf and runs it.
So far so go...
Our main application loads multiple swf's and xml's during runtime using http service calls, loaders and style loaders
These all fail due to sand box security violations.
I run the extension using attach as.. in the creative builder.
Any idea how to get around this? why running from the debug folder causes these errors?
I have tried adding cross-domain policy files but that doesn’t seem to help.
Have something to add?
Find more inspiration, events, and resources on the new Adobe Community
Explore Now