Mar 22nd, 2010, 05:16 AM
feature request: support for subapplications
I was trying to load a subapplication with its own container.
But now only modules are supported with their own containers.
Of course loading a subapplication in a sibling applicationDomain would give no problems (you don't need the second parameter in the FlexXmlApplicationContext constructor) but right now we are in transition phase so the subapplications are loaded in a child applicationdomain (for reasons that go beyond the scope of this post).
Any ideas how i can best tackle this?
Is extending the FlexXMLApplicationContext is an option or would this be too complex. I mean classes inside the FlexXMLApplicationContext use the ownerModule too, so i need to extend them too, right?
I think i'll give it a go....
But the question:
What i wondered is why there is an explicit reference to the class Module in FlexXMLApplicationContext? If it would be a UIComponent or DisplayObject things become more flexible (subapps would be supported). You could define contexts like: var context:FlexXmlApplicationContext = new FlexXmlApplicationContext("context.xml", this); So nothing changes in the interface. The context will then figure out for you on which applicationdomain "this" is just like it does for modules now.