Thanks for the reply Cliff.  I thought of the idea of using an internal id after I had posted, but it's good to get confirmation from someone as experienced as you.

I'm having difficulty grappling with a scenario where I have designed a component and a subsequent Mediator for it, then down the road I need to reuse that component as a subcomponent.  It seems like I have no choice but to create a new Mediator class that can deal with the multiple subcomponents. 

A concrete example would a video player application that displays one window for one video.  Then down the road say I want to reuse that video component inside of some tiling component so multiple streams can be displayed simultaneously. 

My first inclination is to create a wrapper Mediator that manages the video display Mediators.  In essence this is what a typical ApplicationMediator in the PureMVC demos, but each of the components are unique. 

In the same way, I'd like to manage multiple instances of one component, but the way Mediators are registered right now I can only have one instance of any given Mediator. 

Does anyone have a good way to approach this scenario?

Hi Cliff,

Thanks for responding and posting a fix so quickly.  I understand your explanation, but I'm wondering what scenario would warrant the removal of a Mediator?  Why have a removeMediator method at all?

Hi Cliff,

I'm not sure if this is a bug or a design issue.  But I ran into an issue with removeMediator not removing the observers created with registerMediator. 

I'm trying to setup a panel that is rarely used in the application but can be opened and closed on demand.  So I'd like to dynamically register the Mediator and add the panel to the stage and subsequently remove the panel and Mediator on close. 

How would you handle this scenario? Is this a bug with removeMediator?

Thanks,
Don