0 Replies Latest reply on Jan 22, 2010 10:36 AM by ZenForHire

    RPC Remote calls fail after loading sibling.

    ZenForHire

      Hi All,

       

      Main loads an app compiled in 3.2. Cannot recompile legacy SWF with version of Main.

      Main and Client are on the same domain. Debugging on localhost.

      Sibling has RemoteObject code but never makes RemoteObject calls.

      Main apps remote calls start failing after sibling is loaded.

       

      TypeError: Error #1034: Type Coercion failed: cannot convert
      mx.messaging.messages::AcknowledgeMessage@c7ab831 to mx.messaging.messages.IMessage.

       

       

      <mx:SWFLoader id="swfLoader"
              loadForCompatibility="true"
              trustContent="false"
              width="100%" height="100%"
              source="ClientGuiApp3-2.swf?fredOn=false"
              complete="swfComplete();"
              creationComplete="initNestedAppProps();"/>

       

      What I have done to try to fix it.

      trustContent = "False" to put it in its own security domain.

       

      I thought loadForCompatability good enough to make them use their own class definitions?

      Document I found says RPC special case for multiversion Sandbox or Bootstrap.

      http://help.adobe.com/en_US/Flex/4.0/html/WS2db454920e96a9e51e63e3d11c0bf69084-7f0c.html

       

      loadForCompatibiity means sandboxing or new security domain for the sibling?

       

       

      Thanks in advance,

      Kevin