I'm sure this has to do with Cairngorm's "issues", but I thought I'd give it a try here anyway.
Got several cairngorm flex apps, trying to use one as the main app and load "one" of the others into it for now. Each app has its own events, commands, delegate, servicelocator, etc. These swfs "DO NOT need to communicate with each other" and they run fine independently. Of course, Cairngorm's issues won't let you load another cairngorm app in the same app domain or else you will get a bunch of "more than one servicelocator...blah blah" errors. So now I'm loading the other swf into a new ApplicationDomain(). It loads without those errors, but now, as soon as the loaded swf tries to make a remote object call, it throws this error: TypeError: Error #1034: Type Coercion failed: cannot convert obj...@125e4039 to mx.messaging.messages.ErrorMessage. Looking at the logs it shows that the loaded swf's remoting call is sending "null" for the destination, and "null" for the operation. It throws this error, no matter which of the other swfs I try to load, once they try to make a remoting call. As I said earlier, these swfs all run fine independently. Anybody who has actually gotten one cairngorm app to load another cairngorm app with remoting, any help would be appreciated. FYI.... I've tried importing the mx.messaging.... classes and using the registerAlias calls in the main app and the loaded apps....but that also doesn't fix the problem.
