Re: Adding transactions info to mdr events

Martin Matula wrote:
> Hi Svata,
> I just don't see why having the transaction events is not enough. That's 
> what I meant by:
> 
Aha. Then I suppose I missed the point of this question:
>>> Why do you need the transaction be passed into events?
I thought that you question transaction events in general, not 
specifically the proposed change to MdrChangeEvent class. Sorry.

It seems that transaction events will be useful for Java model, too -- 
we will most probably need to group some operations. For example 
changing order of methods in a class will generate remove and add events 
on the `ClassFeatures' association, this additional event will allow us 
to map the pair to a true text move, I hope.

Thanks!
-Svata