Cannot convert mx.messaging.messages::AcknowledgeMessage

Question

I need to call upon the wiser people in these forums again. I'm getting the message
TypeError: Error #1034: Type Coercion failed: cannot convert mx.messaging.messages::AcknowledgeMessage@21501561 to mx.messaging.messages.IMessage.
when I call a logout function in my application. But the strange thing is that this only happens if I have loaded a sub-application using SWFLoader and loadForCompatibility=true. My structure is as follows:
an Air app that acts as a wrapper and contains the code for a authentication service. This wrapper loads a core sub-app if authentication is a success. The core is loaded using an SWFLoader with default settings. Inside the core sub-app I have a logout button and a number of states defined in the layout. The logout button is included in all states. When clicked, it dispatches a Logout event, which is caught and handled by the AIR wrapper. One of the states includes a SWFLoader that loads another sub-app (let's call it subA). This basically means the logout button and the SWFLoader are siblings in the same layout (not quite, the SWFLoader is actually a child of another component, but I don't think that makes a difference in this case).
If I load subA using loadForCompatibility=true, I get the error message as stated above. If I set it to false, I don't get the error message. Clearly, this is due to different applicationDomains of the core and subA. What I however don't get is
a) The logout event is dispatched from the core, not from subA, which is in a sibling application domain to the core. How come it makes a difference whether or not I've loaded something into the SWFLoader and whether or not it's been loaded into a child or sibling application domain of the core?
b) These classes are both part of the mx package and thus part of the flex framework (?), shouldn't they be marshalled automatically?
Once again, apprechiate any responses that could shed some light on this for me.

Answer 1

You should create a bootstaploader according the adobe documents:
http://livedocs.adobe.com/flex/gumbo/html/WS2db454920e96a9e51e63e3d11c0bf69084-7f06.html
but i tried that but it doesn't work. LoadForCompatibilty is still the issue.
So i have a bootstraploader which has all the remoting stuff in it just as described in the adobe document referered to above. Then it loads my main application which has a remote object in it. Calling the remote object goes fine. If that main application loads a sub application with a remote object, both don't work anymore.
This is only the case if the sub application is loaded in a sibling application domain (which is the same as setting load for compatibility set tot true of the swfloader). If it's loaded ain a child domain of the main application domain it works. The problem is we are need our modules to be flexible and that they can be compiled wth different versions of the flex framework. It should be possible as this is what the marshal plan is all about right?
if i load the subapplication (in compatibility mode) and call the remote method on the sub application i get the next error:
TypeError: Error #1034: Type Coercion failed: cannot convert Object@1c9c3089 to mx.messaging.messages.ErrorMessage.
but it's application domain should be a direct child of the bootstrapper application domain so it should have the mx.messaging.messages.ErrorMessage. Somehow this fails. And even worse the main application gets screwed too. Because if i just load the subapplication and don't call the remote object, but directly after loading it i call a method on the remote object defined in main i get another similar error:
TypeError: Error #1034: Type Coercion failed: cannot convert mx.messaging.messages::AcknowledgeMessageExt@19b11e49 to mx.messaging.messages.IMessage.
This is clearly undesired behavior. Can someone from adobe shed a light on this?
thanx Arnoud