Bugzilla – Full Text Bug Listing
| Summary: | JM - Builders and nested operations using Java model can get inconsistent results (1FUBV90) | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Nick Edgar <n.a.edgar> |
| Component: | Core | Assignee: | Jerome Lanneluc <jerome_lanneluc> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P4 | ||
| Version: | 2.0 | ||
| Target Milestone: | 2.0 M1 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
PRODUCT VERSION: M-050100H11 Is this one still an issue ? 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. |
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.