Seems when working with puremvc and flex events there are some hangups, in that not all events are useable. The one I found was that creationComplete event triggered by modules. What I wanted was to be able to populate certain dropdowns from database dynmically. The onload event triggered prior to onregister function in the mediator. Documented is the lifecycle.
* Mxml creation
* View components
* Facade
* PureMVC startup
* Register proxies
* Register mediators
* Request data
* Proxy method (such as 'load') invoked by mediator or command
* Proxy calls service directly or uses a delegate to do so.
* Receive data
* Proxy recieves result/fault return
* if result then Proxy stores data internally, parsing if need be, possibly using a helper.
* Proxy sends result or fault notification.
* Interested mediators respond by setting data on view component.
* View components
* Facade
* PureMVC startup
* Register proxies
* Register mediators
* Request data
* Proxy method (such as 'load') invoked by mediator or command
* Proxy calls service directly or uses a delegate to do so.
* Receive data
* Proxy recieves result/fault return
* if result then Proxy stores data internally, parsing if need be, possibly using a helper.
* Proxy sends result or fault notification.
* Interested mediators respond by setting data on view component.
To get around this I used a puremvc plugin called startup manager.
introduction to startup manager
Creation complete
--post defined by cliff creator of puremvc
Link to puremvc forums about topic
