Did you actually try it and found that it fails? I would think it should be able to introspect child appdomains.
From: Nigel Magnay <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Friday, September 27, 2013 6:36 AM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: [flexcoders] Automation and Application Domains We are using RIAtest, which uses flex automation to test some applications. Reading the flex documentation, it contains the following: Testing applications that load external libraries ... A library that is loaded at run time (including run-time shared libraries (RSLs)) must be loaded into the ApplicationDomain of the loading application. If the SWF file used in the application is loaded in a different application domain, automated testing record and playback will not function properly. This is particularly inconvenient for us; we load UI controls into separate ApplicationDomains (all children of ApplicationDomain.currentDomain) because they can have conflicting classnames, and this allows each form to be generated in isolation, and they cannot interfere with each other. The thought of having to refactor hundreds of classes is not appealing. This seems to prevent RIAtest's inspector from finding child controls sourced from that loader. Is there any way around this restriction, perhaps by implementing some kind of delegate class, or overriding the automation provider to allow it to callback to discover the applicationdomains it needs to search?
