Re: Changes to Events API

Hi Holger,

Holger Krug wrote:
> I like this. On the other hand is there any implementation
> (e.g. performance) reason to restrict this to references from
> component to composite. The composition relation is introduced by the
> meta-modeler and might not be the right thing for the applications on
> the model level.

The same you could say about other things that component semantics 
involves and regular references not (such as recursive delete, 
reflective operations like refImmediateComposite, etc.). So I think that 
binding this feature to the composition semantics is the right thing to 
do - logicaly it means that object changes if any of its components change.
In addition, this can be implemented very effectively in MDR, since each 
object has only one composite and it is stored directly in the object.

>>Now the question is, how the listeners should register for the events 
>>from containers. I would like to add method addListener(..., boolean 
>>includeComponents), however this would be applicable only for 
>>registering listeners on RefObjects. Should there be a special 
>>RefObjectEventSource for RefObjects? Any suggestions are welcome.
>>Martin
> 
> In your case I would add a flag in the bitmask instead of introducing
> a new method.

I agree.
Thanks,
Martin