Hi, have you found the solution? I'have the same problem with crossdomain.xml ...
Your BlazeDS app should be accessible externally (from internet). Internal IP would work only on your network.
Yeah, in the end I had to expose the BlazeDS server so it is externally accessible. I didn't want to do that, but I think it is the only way to do it.
I deploy the application in a production environment and i can't modify that server.. I can only deploy file under the context-root.This is a great limitation ov flex!
How is the BlazeDS server made externally accesssible? I am having the same problem and meddling with this problem from the past couple of days.
This is my crossdomain.xml file
<!DOCTYPE cross-domain-policy SYSTEM "http://www.macromedia.com/xml/dtds/cross-domain-policy.dtd">
<allow-access-from domain="*" secure="false" />
I have my flex app installed in tomcat and trying to access java application installed on a server using AMF