Futurescale, Inc. PureMVC Home

The PureMVC Framework Code at the Speed of Thought

Over 10 years of community discussion and knowledge are maintained here as a read-only archive.

New discussions should be taken up in issues on the appropriate projects at https://github.com/PureMVC

Pages: [1]
Author Topic: Chaining mediator registration not working?  (Read 14657 times)
Posts: 3

View Profile Email
« on: October 22, 2012, 11:46:34 »

I am trying to register a view component with a mediator, then in the onRegister method of the mediator, I'm trying to register another component with another mediator. The first onRegister is called, yet the next is not.

So something like:

override public function onRegister(): void
   facade.registerMediator( new AppMediator( app ) );

=== Then, inside AppMediator ===

override public function onRegister(): void
   facade.registerMediator( new GameMediator( app.game ) );

There is obviously an app helper in the AppMediator. The first onRegister() gets called by the facade but the second onRegister() doesn't get called by the facade.

Any explanation, I thought this was standard practice?

Gary Paluk

P.S. All other objects exist and are tested to be instantiated.
Global Moderator
Hero Member
Posts: 2871

View Profile WWW Email
« Reply #1 on: October 22, 2012, 05:11:00 »

Hi Gary,

This is definitely standard practice.

But it looks a little strange, what mediator is the first onRegister() a part of? The one that registers AppMediator?

It seems weird that the AppMediator wouldn't be registered by the StartupCommand.execute() method (passing in the app from the note body), and the GameMediator be subsequently registered by the AppMediator.onRegister().

Can you provide more context, e.g., the order of events that happens in your startup?

Pages: [1]