Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 137503 - TransactionChangeRecorder resolves containment proxies
Summary: TransactionChangeRecorder resolves containment proxies
Status: VERIFIED FIXED
Alias: None
Product: EMF Services
Classification: Modeling
Component: Transaction (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P1 blocker
Target Milestone: ---   Edit
Assignee: Christian Damus CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-19 10:41 EDT by Christian Damus CLA
Modified: 2017-02-24 15:10 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Damus CLA 2006-04-19 10:41:29 EDT 
The TransactionChangeRecorder resolves containment proxies when it propagates itself to the contents of an element.  This causes aggressive loading of resources which it is imperative to delay in models of the 10s or 100s of MBs range.

There is a TODO already on the spot  :-)
Comment 1 Christian Damus CLA 2006-04-21 11:16:18 EDT 
Committed a fix.  As a side-effect, the TransactionChangeRecorder also will no longer:

  - record changes due to resource load or unload (which are not really
    undoable operations, anyway)
  - forward notifications to the active transaction for validation, triggers,
    and notification that originate from objects being loaded or unloaded

The latter change helps performance a little bit and also ensures that triggers and validation do not interfere with resource loads:  the loaded resource will have the same state as when it was saved, without triggers potentially reacting to notifications and erroneously making additional changes.
Comment 2 Nick Boldt CLA 2008-01-28 16:35:37 EST 
Move to verified as per bug 206558.