[news.eclipse.tools.emf] Re: Suppress Notification and containment list

[Ed Merks <Ed.Merks@xxxxxxxxx>]

Artem,

Comments below.

Artem Tikhomirov wrote:
> Ed,
>
> Well, I thought containment is kind of fundamental relation, and 
> eContainer() not null for contained object seems reasonable expectation,
One person's fundamental seems to be another person's complex/unnecessary...
> even if it causes few(?) extra implementation classes.
No, not just a few.  Enough to cause a significant of bloat....
> > > Am I wrong assuming Suppress Notification should not affect 
> > > bi-directionality of the containment? 
> > Wrong is perhaps too strong a word, but certainly you're expectations 
> > are too high.  What exactly are you hoping to gain by suppressing 
> > notifications?
>
> With Suppress Notification option, I try to get a model that is 
> instantiated once, processed (read), and discarded. 
If there are no listeners, notifications aren't produced so I'm not sure 
there's much to be gained.
> There are no model modifications expected (other than assembling or 
> reading/loading it from resource), hence no notifications needed. I 
> understand that eNotificationRequired() is effective and is not too 
> much code to get rid of, nevertheless, once you face an obstacle, it's 
> out of curiosity to find out ;)
It's not worth worrying about, in my opinion.
> Thanks.
>
> Artem.