Hello Jukka...sorry I missed your message from (way back) in January. Did you ever find the answer you were looking for?
--- In flexcoders@yahoogroups.com, Siluetti <hamalainen.ju...@...> wrote: > > > Hi, > > I'm running into this same error with Mate framework, so this is not only > Cairngorm-related problem. Trying to make RPC-calls via sub-application > loaded with swfloader gives the same error as previously described: > > "No destination with id 'null' is registered with any service." > > Also I get the same Error: > > "TypeError: Error #1034: Type Coercion failed: cannot convert obj...@a0caee9 > to mx.messaging.messages.ErrorMessage." > > Tried the Security.allowDomain as described in the pdf, but nothing. Erich, > did you manage to fix this? > > Cheers, Jukka > > > Erich Cervantez wrote: > > > > Thanks for the link... > > > > I've seen that PDF before but hadn't read up to page 40. It's first > > suggestion recommended loading the sub-application as a sandboxed > > application by calling Security.allowDomain() in the main application and > > calling it also on the sub-application's pre-initialization event. > > Unfortunately there's no difference. > > > > > > --- In flexcoders@yahoogroups.com, "Gordon Hirsch" <gordon.hirsch@> > > wrote: > >> > >> Have you seen the section titled "Using RPC and DataServices classes with > >> multi-versioned applications" (~p. 40) in this document? > >> > >> http://livedocs.adobe.com/flex/3/loading_applications.pdf > >> > >> If I understand correctly, you are hitting this issue and will need > >> either to use sandboxing or a bootstrap loader. > >> > >> Like you, we have been struggling with sub-applications. For example, > >> it's not clear from the documentation exactly which classes are safe to > >> use in a bootstrap loader. Does anyone have details on what's legal and > >> what's not? > >> > >> --- In flexcoders@yahoogroups.com, "Erich Cervantez" <flex@> wrote: > >> > > >> > The key thing to note: both applications are able to dispatch service > >> calls on their own when called separately through a browser. Both > >> applications work great on their own. > >> > > >> > Currently, I'm pointing the "source" attribute on SWFLoader to the swf > >> location of the sub-application. I'm loading the app into a peer > >> Application Domain (I believe, on the same "level" as the parent > >> application - both children of the System Domain): > >> > > >> > _loaderContext.applicationDomain = new ApplicationDomain(); > >> > mySubApplication.loaderContext = m_loaderContext; > >> > mySubApplication.source = "http://xyz:8080/xyz/MySubApp.swf";; > >> > > >> > I've tried loading the sub-swf into the same App domain, but since > >> they're both Cairngorm apps and use the Cairngorm ServiceLocator > >> singleton, I get the typical singleton error ("only one servicelocator > >> can be instantiated"). > >> > > >> > My next option might be to assemble most of the logic in the sub-app > >> into a module. My primary app can load the module and use it's own > >> service framework for remoting (assuming I can get this to work). I can > >> create a separate, light-weight shell container with its own service > >> framework that can also load the same module whenever I want to use the > >> sub-application by itself. > >> > > >> > Googling this issue isn't working...I have to assume someone out there > >> is creating portal applications that load small sub-apps (in Cairngorm). > >> I have to figure out how they solved this problem... > >> > > >> > > >> > > >> > --- In flexcoders@yahoogroups.com, Maciek Sakrejda <msakrejda@> wrote: > >> > > > >> > > The 'destination null' seems to imply that your Flex-side remoting > >> > > metadata is fubared. It's trying to contact a destination that was > >> not > >> > > configured--or somehow got unconfigured through the peer-appdomain > >> swf > >> > > loading. I've asked about doing something similar with Modules, and > >> was > >> > > told by Adobe folks on the list that this would be a Bad Idea. > >> However, > >> > > I believe they suggested separate apps--just as you are doing. Have > >> you > >> > > tried loading the .swfs into the same appdomain? > >> > > -- > >> > > Maciek Sakrejda > >> > > Truviso, Inc. > >> > > http://www.truviso.com > >> > > > >> > > -----Original Message----- > >> > > From: Erich Cervantez <flex@> > >> > > Reply-to: flexcoders@yahoogroups.com > >> > > To: flexcoders@yahoogroups.com > >> > > Subject: [flexcoders] Cairngorm sub-applications & Remoting > >> > > Date: Thu, 16 Apr 2009 17:01:51 -0000 > >> > > > >> > > > >> > > > >> > > Has anyone written two distinct Cairngorm-based applications, each > >> > > capable of dispatching service calls (via RemoteObject) and tried > >> > > loading one inside of the other? > >> > > > >> > > Essentially I have a parent application that uses SWFLoader to load a > >> > > sub-application (in a peer Application Domain). The sub-application > >> > > loads visually within the parent application but service calls from > >> the > >> > > sub-application result in a runtime error: > >> > > > >> > > TypeError: Error #1034: Type Coercion failed: cannot convert > >> > > obj...@xxxxx to mx.messaging.messages.ErrorMessage. > >> > > > >> > > JBOSS logs show this: > >> > > > >> > > No destination with id 'null' is registered with any service. > >> > > > >> > > The first error appears to be a class-aliasing problem, but both of > >> > > these apps are Cairngorm-based Flex applications...the > >> > > registerClassAlias method shouldn't be required (besides, I tried > >> that > >> > > tactic already to no avail). > >> > > > >> > > This is the only Flex-equivalent of a bat-signal I can think of ;) > >> > > > >> > > Erich > >> > > > >> > > >> > > > > > > > > > > -- > View this message in context: > http://old.nabble.com/Cairngorm-sub-applications---Remoting-tp23082422p27326317.html > Sent from the FlexCoders mailing list archive at Nabble.com. >
