tag:robotlegs.tenderapp.com,2009-10-18:/discussions/robotlegs-2/10020-problems-with-mediator-mapping-when-using-multiple-inheritanceRobotlegs: Discussion 2014-03-17T13:59:48Ztag:robotlegs.tenderapp.com,2009-10-18:Comment/317678542014-02-24T17:14:32Z2014-03-17T13:59:48ZProblems with Mediator mapping when using multiple inheritance<div><p>As often, I eventually found a solution myself after posting it
online. Still, it may help others.</p>
<p>Using<br>
mediatorMap.map(BaseItem).toMediator(BaseMediator); deactivating
the <em>VigilanceExtension</em> and setting LogLevel to WARN in the
Bundle removes all unwanted output.</p>
<p>However, I don't think that using above mapping should produce a
warning at all.</p></div>emailtag:robotlegs.tenderapp.com,2009-10-18:Comment/317678542014-02-25T08:42:50Z2014-02-25T08:42:50ZProblems with Mediator mapping when using multiple inheritance<div><p>Hey Reinbert,</p>
<p>Your first post got stuck into the spam filter of the forum.
I've restored it.</p>
<p>This should work just fine:<br>
mediatorMap.map(BaseItem).toMediator(BaseMediator);</p>
<p>I'll take a look at your attached project and report back my
findings</p>
<p>Ondina</p></div>Ondina D.F.tag:robotlegs.tenderapp.com,2009-10-18:Comment/317678542014-02-25T10:22:02Z2014-02-25T10:22:02ZProblems with Mediator mapping when using multiple inheritance<div><p>I looked at your classes.<br>
You're adding child views inside of the set data() method.<br>
I added a handler for (each) view's ADDED_TO_STAGE, where I added
their child-views. (Note: I was overriding an addedtostage handler
of the BaseView in the derived views)<br>
That seems to work. Each view has its own BaseMediator.</p>
<p>The mapping is :
mediatorMap.map(BaseItem).toMediator(BaseMediator);</p>
<p>and [Inject] public var view:BaseItem; is injected into
BaseMediator</p>
<p>Try it out and let me know how it goes.</p>
<p>Ondina</p></div>Ondina D.F.