Thanks for the great suggestions, I'll let you know how the cross domain.xml 
and 2nd param for createworker works out.

On Aug 14, 2013, at 12:49 AM, Carl Kelvin <carl_b...@yahoo.com> wrote:

> No. Its a different file. You have to create a file like this:
> 
> "<?xml version="1.0"?>
> <!DOCTYPE cross-domain-policy 
>  SYSTEM "http://www.macromedia.com/xml/dtds/cross-domain-policy.dtd";>
> <cross-domain-policy>
>   <allow-access-from domain="*.googlegroups.com" />
> </cross-domain-policy>"
> 
> And save it as crossdomain.xml and save it where your blazeds was.
> 
> Anyway you can read this article for reference.
> http://tgeorgiev.blogspot.com/2010/01/flex-spring-blazeds-integration-on-web.html
> 
> 
> 
> 
> ________________________________
> From: Mark Line <markl...@gmail.com>
> To: users@flex.apache.org; 'Carl Kelvin' <carl_b...@yahoo.com> 
> Sent: Wednesday, August 14, 2013 3:36 PM
> Subject: RE: cross domain issue with AS3 worker
> 
> 
> When you are creating the worker are you passing true as the 2nd parameter to 
> give the app permissions? 
> 
> WorkerDomain.current.createWorker(Workers.name, true);
> 
> -----Original Message-----
> From: Carl Kelvin [mailto:carl_b...@yahoo.com] 
> Sent: 14 August 2013 06:40
> To: users@flex.apache.org
> Subject: Re: cross domain issue with AS3 worker
> 
> Hi;
> 
> Do you have a crossdomain.xml? If not try to create. Its just a small file 
> that gave you the access for cross domain
> 
> 
> ________________________________
> From: Adrian Gillette <gille...@adrian.net>
> To: users@flex.apache.org 
> Sent: Wednesday, August 14, 2013 1:00 PM
> Subject: cross domain issue with AS3 worker
> 
> 
> HI everyone,
> 
> I'm helping someone with their Flex project, in which they're attempting to 
> offload the logic for making API calls to a blazeDS server and processing the 
> response to a worker swf.  In making the API call from the worker swf, 
> blazeDS is responding with the following error "…  denied due to lack of 
> policy file permissions."  Any ideas on how to fix this?
> 
> A

Reply via email to