That's definitely an option. Still, I'd like to know why remoting isn't working from the sub-application. Is it Cairngorm design flaw or...?
--- In [email protected], Pedro Sena <sena.pe...@...> wrote: > > Hi, > > In my opinion you should try to change your small application to a flex > module. > > You could develop a very small "shell" that load this module, to use it > standalone, and when using it from your big app, you simply loads this > module. > > Just take care when you use this together: Cairngorm and Modules. > > PS > > On Wed, Apr 15, 2009 at 3:53 PM, Erich Cervantez <f...@...> wrote: > > > > > > > I have a large Flex 3.3 application configured to use LCDS within a JBOSS > > war. I've setup RemoteObject declarations using Cairngorm's ServiceLocator > > pattern. The application works great and is able to send and receive data on > > it's own just perfectly. > > > > I also have a separate smaller Flex 3.3 application in a different war > > configured similarly. > > > > Although both applications can be used individually, I'd like to load the > > smaller application into the first, larger application using SWFLoader (and > > setting the LoaderContext to use a new ApplicationDomain). > > > > Unfortunately, the sub-application cannot make any service calls now and > > I'm at a loss. I figure it might be some sort of sandbox issue but I'm not > > sure. > > > > The exception thrown via JBOSS looks like this: > > > > "No destination with id 'null' is registered with any service." > > > > and the runtime exception in the browser looks like this: > > > > "TypeError: Error #1034: Type Coercion failed: cannot convert > > obj...@1b434ad9 to mx.messaging.messages.ErrorMessage." > > > > Has anyone else run into this same situation? > > > > > > > > > > -- > /** > * Pedro Sena > * Systems Architect > * Sun Certified Java Programmer > * Sun Certified Web Component Developer > */ >
