Summary: | Java Model Exceptions in log from TypeHierarchyLifeCycle | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Nick Edgar <n.a.edgar> |
Component: | Core | Assignee: | Jerome Lanneluc <jerome_lanneluc> |
Status: | RESOLVED WORKSFORME | QA Contact: | |
Severity: | normal | ||
Priority: | P2 | CC: | martinae |
Version: | 1.0 | ||
Target Milestone: | 2.0 M3 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
Nick Edgar
2001-12-21 12:58:20 EST
I had this bug many times too. Couldn't reproduce on 20109 though. Problem is that JavaElementDelta of a CU reports CU to be changed, but accessing it result in a 'does-not-exist' exception. Philippe, was there any change on this? Can I asume that elements that are reported to be changed are existing, or should I add a exists test? I am suspecting this is a duplicate of 8359. Did these happen after having upgraded your workspace (newer JARs from a more recent build) and without exiting/restarting ? We are aware of some issues there, where indexes would not be refreshed properly, and thus allowing to recreate Java element handles for no longer existing elements (e.g. hierarchies could expose these, or open type dialog). Can you confirm these symptoms ? As indicated, I had been opening hierarchies. I probably did upgrade to the latest build without replacing the workspace. However, I always shutdown before updating. |