Bug 3183 - JM - Builders and nested operations using Java model can get inconsistent results (1FUBV90)
Summary: JM - Builders and nested operations using Java model can get inconsistent res...
Status: RESOLVED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: All All
: P4 normal (vote)
Target Milestone: 2.0 M1   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-10-10 22:50 EDT by Nick Edgar CLA
Modified: 2002-01-14 11:08 EST (History)
0 users

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 Nick Edgar CLA 2001-10-10 22:50:53 EDT 
The JavaModel relies on notification to update the children of package fragments and package fragment roots.
This can give inconsistent results for builders, or within nested operations.

For example:

The workspace has
SomeSolution/
  SomeProject/
    java/
      lang/
        Object.java
    p1

The Java Model is consistent with this, with a source root at project level.
Run the following:

begin nested operation
ask Java Model if package p1 exists
	-> true
delete folder p1
ask Java Model if package p1 exists
	-> true  (because it hasn't gotten notification yet)
get children of p1
	-> NotPresentException thrown
end nested operation
ask Java Model if package p1 exists
	-> false (because it got notification after the end nested operation)

NOTES:

JBL (6/19/2001 5:22:10 PM)
	Potential problem still there.
Comment 1 DJ Houghton CLA 2001-10-23 23:50:52 EDT 
PRODUCT VERSION:
M-050100H11
Comment 2 Philipe Mulet CLA 2001-12-10 17:57:09 EST 
Is this one still an issue ?
Comment 3 Jerome Lanneluc CLA 2001-12-11 05:43:18 EST 
During nested operations, we cannot get resource deltas. It would be the same 
behavior as if the folder was deleted using java.io.File.delete(). There is 
nothing we can do about it. Closing.