|
I got it, but still don’t know how.
I fought with it all afternoon and it just decided to work. But I’ll
take it. Now to get it going at the client site… Tract From: Ok, it is a security issue: “Cross-movie scripting also occurs when an HTML page uses
_javascript_ (or another scripting language) to script a Macromedia Flash
movie—for example, by calling And the solution is: System.security.allowDomain( "www.mysite.com" ); Now lets see if I can make it work… From: I
have determined my setVariable problem(it does not
communicate with the app) is the result of the way I specify the application
swf in the custom wrapper. This
source
reference using “localhost” works: <param name='src' value='http://localhost:8700/flex/apps/myApp.mxml.swf'> This one using the server name
does
NOT: <param name='src' value='http://MyServerName:8700/flex/apps/myApp.mxml.swf'> In this test case, myApp is really on local host (still breaks),
but at the customers site, the Flex server is on a different box than the web
server. Is this a known issue? Any suggestions? I can’t put the myApp
swf
on the web server because I am using the flex server proxy for named services,
can I? Licensing aside for now(cust. has full
license), is it possible to have the swf on a different box than the Flex
server and still use the flex proxy? I though about using the dhtml->gateway.swf
flashvars->local connection->myApp solution, but I am afraid local
connection might not work either, under my scenario. Any ideas will be appreciated.
|
Title: setVariable: only works on localhost?
