Make sure you have loaded the modules correctly. You have to specify the
applicationDomain of the nested module otherwise it will become a sibling.
On 4/9/12 2:35 PM, BillF bill.frank...@bayer.com wrote:
Flex SDK v3.6
Okay, I have a module that is called from an application. That
Thanks Alex,
Is there a time when you wouldn't want to put ApplicationDomain.currentDomain
in the IModuleInfo.load call?
Freundliche Grüße / Best regards,
Bill Franklin
Computer Integrated Mfg.
[cid:image001.gif@01CD16F9.19A16DD0]
Bayer CropScience LP
8400 Hawthorne Road, Room 2447
Kansas
Actually, you have four commonly used options whenever a parameter or property
is of type ApplicationDomain:
null
new ApplicationDomain()
ApplicationDomain.currentDomain
new ApplicationDomain(ApplicationDomain.currentDomain)
New ApplicaitonDomain() will never work for modules.
Thanks...I think that clears it up.
So, if I am understanding correctly, for consistency, I should call .load(new
ApplicationDomain(ApplicationDomain.currentDomain)); for module loads inside of
modules, and from inside the main application as well (since apparently that is
the same thing that
Yes, that is correct.
On 4/10/12 8:49 AM, Bill Franklin bill.frank...@bayer.com wrote:
Thanks…I think that clears it up.
So, if I am understanding correctly, for consistency, I should call .load(new
ApplicationDomain(ApplicationDomain.currentDomain)); for module loads inside of
modules,
Flex SDK v3.6
Okay, I have a module that is called from an application. That module calls
another module. Trying to run any RemoteObjects from the nested module is
failing, resulting in the following error:
TypeError: Error #1034: Type Coercion failed: cannot convert Object@d3dcad9 to
6 matches
Mail list logo
