The option exists so you can choose a child topology (default) or same domain toplogy (RSL). Yes that means you can stick in parameters for a separate appdom, but since modules must share interfaces, you can hopefully see why that will never work.
You can check out the Marshall Plan if you have a strong reason to use separate appdoms. Alex Harui Flex SDK Developer Adobe Systems Inc.<http://www.adobe.com/> Blog: http://blogs.adobe.com/aharui From: [email protected] [mailto:[email protected]] On Behalf Of Manish Jethani Sent: Thursday, May 14, 2009 4:10 PM To: [email protected] Subject: Re: [flexcoders] Loading Modules in Separate Application Domains On Fri, May 15, 2009 at 2:04 AM, colin.shreffler <[email protected]<mailto:cshreffler%40gmail.com>> wrote: > ModuleManager.getModule(_url).load(new ApplicationDomain(), > SecurityDomain.currentDomain) > > As soon as I do this however, I am getting the following error: > > "SWF is not a loadable module" > > If I use ModuleManager.getModule(_url).load() it works fine but then I have > the issue of each module running in a shared ApplicationDomain which isn't > what I want. It doesn't look like this is supported: you can't load the module in a separate application domain (which makes me wonder why the option exists at all). http://www.mail-archive.com/[email protected]/msg80560.html Manish
