Home → Problems →

App mediator not instantiated, but only ONLINE

• Edit

creynders

05 Oct, 2010 07:40 AM

I've encountered something weird, I'm creating a site in FB3 with RL and everything works fine locally, but when I upload everything online suddenly the app Mediator is not instantiated.
Everything runs just as expected except the app Mediator is not created... ??
I haven't got the faintest idea what could be wrong, anybody has any bright ideas??

1. Support Staff 1 Posted by Ondina D.F. on 05 Oct, 2010 07:46 AM

   

   Hi creynders,

   take a look at :
   http://github.com/robotlegs/robotlegs-framework/wiki/Common-Problem...
   (the metadata will stay intact while debugging but will be stripped out when you publish your release build)

   Does it help?
   Ondina

   • Edit

2. Support Staff 2 Posted by Ondina D.F. on 05 Oct, 2010 07:49 AM

   

   or this:
   http://knowledge.robotlegs.org/faqs/reference-mvcs-implementation/c...

   • Edit

3. Support Staff 3 Posted by Ondina D.F. on 05 Oct, 2010 08:00 AM

   

   or you'd have to create the Mediator like this:
   

   override public function startup():void
   {
       mediatorMap.mapView(MediateApplicationExample, AppMediator);
       mediatorMap.createMediator(contextView);
   }
   

   see: http://github.com/robotlegs/robotlegs-framework/wiki/best-practices... (Mapping the Main Application (contextView) Mediator)

   • Edit

4. Support Staff 4 Posted by creynders on 05 Oct, 2010 08:16 AM

   

   I'm using the .swc so normally the required compiler arguments are included.

   And, I've been testing a little more and it gets crazier by the minute.
   Originally I used:
   

   <backoffice:AppContext contextView="{ Application.application.systemManager }" />

   (using this, I don't have to instantiate the popup mediators manually) and it works fine debugging straight in FB, w/o using a webserver, but once served by a webserver, it fails to create the app mediator.
   So I switched to
   

   <backoffice:AppContext contextView="{ this }" />

   And now it does create an app mediator in both cases, but it fails to create some other mediators (!!!)
   ... very weird ...

   Alas,
   

   mediatorMap.createMediator(contextView);

   didn't solve anything...

   • Edit

5. Support Staff 5 Posted by Ondina D.F. on 05 Oct, 2010 08:28 AM

   

   You are talking about popup mediators?

   Then maybe this will help:)
   http://knowledge.robotlegs.org/faqs/reference-mvcs-implementation/h...

   Ondina

   • Edit

6. Support Staff 6 Posted by Ondina D.F. on 05 Oct, 2010 08:39 AM

   

   It would be better if you posted the code for the mapping and for the instatiation of your context in your root View (Application)
   

   • Edit

7. Support Staff 7 Posted by creynders on 05 Oct, 2010 08:40 AM

   

   Well, no, I wasn't really talking about mediating popups. I mean, yes I do mediate popups, but that's not causing the problem, I just mentioned it so you'd know WHY I use Application.application.systemManager, instead of this

   In the meantime I found a solution of some sorts. If I map the AppMediator earlier on in my bootstrap sequence, then it does work in all cases. That goes against
   

   To avoid unexpected behavior it is recommended that you map your context mediator last. but apparently I've got no other choice. However, I don't like it, since I've got a feeling it can suddenly break again...

   • Edit

8. Support Staff 8 Posted by Ondina D.F. on 05 Oct, 2010 08:55 AM

   

   Well then this is a special case:
   Application as the contextView vs. SystemManager as the contextView.
   I’m sure Stray or Shaun or someone else will help you with this.

   • Edit

9. Support Staff 9 Posted by creynders on 05 Oct, 2010 09:12 AM

   

   Thanks for taking your time and helping out, BTW!

   • Edit

10. Stray closed this discussion on 10 Feb, 2011 05:54 PM.