Bug 5542 - Too many deltas are fired on each JavaModel operation
Summary: Too many deltas are fired on each JavaModel operation
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P2 normal (vote)
Target Milestone: 2.0 M1   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 3215 (view as bug list)
Depends on:
Blocks:
 
Reported: 2001-11-05 12:58 EST by Philipe Mulet CLA
Modified: 2002-01-14 11:50 EST (History)
1 user (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 Philipe Mulet CLA 2001-11-05 12:58:48 EST 
Build 207

When creating a compilation unit through a JavaModel operation, 2 deltas
are notified (create CU, add type), then a fine grain delta is notified.

Then, an bonus one is sent when the resource delta comes back through the
delta processor. This one is non sense and should be filtered out by the
Delta processor.
Comment 1 Jerome Lanneluc CLA 2001-12-07 06:12:51 EST 
Reworked the firing of IJavaElementDeltas by batching them.
Java model operations now only create deltas (they don't automatically fire 
them). If a java model operation modifies any resources, let the delta 
processor do the merging of the deltas and the firing. If the java model 
operation doesn't modify any resources (like the SetClasspathOperation), do the 
firing right away.
Comment 2 Jerome Lanneluc CLA 2001-12-11 05:27:41 EST 
*** Bug 3215 has been marked as a duplicate of this bug. ***