Another, more specific question here: If my main application defines a set of AMF endpoints in the services-config.xml file, but it can load arbitrary modules which can specify their *own* AMF endpoints, is there a sensible way to manage that? It seems like I need a single services-config.xml file, but that means I would have to rebuild the main app (against the new services config file) if modules want to add their own endpoints. Is there a way to work around this?
-Maciek On Sat, 2008-10-18 at 00:28 -0700, Maciek Sakrejda wrote: > I'm trying to refactor some parts of our existing app into Flex > Modules, > and, more importantly, simplify further extensions through supporting > Modules. I've been reading up the Adobe docs on this, and it seems > reasonably straightforward, but I wanted to ask if there are any > gotchas > and such to watch out for. > > Also, Singletons defined in the parent application will "just work", > right? Since the child app domain will reuse those definitions, I > don't > need to worry about two separate Singleton instances in case (parent > and > child), right? > > Thanks, > -- > Maciek Sakrejda > Truviso, Inc. > http://www.truviso.com > > > > >
