Bug 5029 - Internal Error saving java file
Summary: Internal Error saving java file
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 2.0 M3   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-10-16 16:15 EDT by John Arthorne CLA
Modified: 2002-02-13 11:25 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John Arthorne CLA 2001-10-16 16:15:26 EDT
Build 203.

Unfortunately I haven't got much to go on... I found this stack trace in my log 
from earlier today.  I have just been editing and saving various java files.  
The files have generally been quite broken (missing superclasses, etc).  I also 
changed the package declarations of several files (may or may not be important). 
 I don't recall getting prompted with an error dialog.

4 org.eclipse.jdt.ui 1 Internal Error
Java Model Exception: Java Model Status [build does not exist.]
	at 
org.eclipse.jdt.internal.core.JavaElement.newNotPresentException(JavaElement.jav
a:442)
	at 
org.eclipse.jdt.internal.core.JavaElement.openHierarchy(JavaElement.java:471)
	at 
org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java(Compil
ed Code))
	at 
org.eclipse.jdt.internal.core.SourceMethod.isConstructor(SourceMethod.java(Compi
led Code))
	at 
org.eclipse.jdt.internal.ui.viewsupport.JavaSourceElementSorter.category(JavaSou
rceElementSorter.java(Compiled Code))
	at 
org.eclipse.jdt.internal.ui.typehierarchy.MethodsViewer$MethodsViewerSorter.comp
are(MethodsViewer.java:74)
	at 
org.eclipse.jface.viewers.TableViewer.indexForElement(TableViewer.java(Compiled 
Code))
	at org.eclipse.jface.viewers.TableViewer.add(TableViewer.java:98)
	at 
org.eclipse.jdt.internal.ui.typehierarchy.MethodsContentProvider.processChangeOn
Input(MethodsContentProvider.java:272)
	at 
org.eclipse.jdt.internal.ui.typehierarchy.MethodsContentProvider.processDeltaWit
houtHierarchy(MethodsContentProvider.java:214)
	at 
org.eclipse.jdt.internal.ui.typehierarchy.MethodsContentProvider.processDeltaWit
houtHierarchy(MethodsContentProvider.java:220)
	at 
org.eclipse.jdt.internal.ui.typehierarchy.MethodsContentProvider.elementChanged(
MethodsContentProvider.java:173)
	at 
org.eclipse.jdt.internal.core.JavaModelManager.fire(JavaModelManager.java:255)
	at 
org.eclipse.jdt.internal.core.JavaModelManager.runOperation(JavaModelManager.jav
a:872)
	at 
org.eclipse.jdt.internal.core.JavaElement.runOperation(JavaElement.java:508)
	at org.eclipse.jdt.internal.core.WorkingCopy.commit(WorkingCopy.java:43)
	at 
org.eclipse.jdt.internal.ui.javaeditor.CompilationUnitDocumentProvider.doSaveDoc
ument(CompilationUnitDocumentProvider.java:283)
	at 
org.eclipse.ui.texteditor.AbstractDocumentProvider.saveDocument(AbstractDocument
Provider.java:357)
	at 
org.eclipse.ui.texteditor.AbstractTextEditor$7.execute(AbstractTextEditor.java:1
287)
	at 
org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.j
ava:64)
	at 
org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1232)
	at 
org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.jav
a:78)
	at 
org.eclipse.ui.texteditor.AbstractTextEditor.performSaveOperation(AbstractTextEd
itor.java:1305)
	at 
org.eclipse.jdt.internal.ui.javaeditor.CompilationUnitEditor.performSaveOperatio
n(CompilationUnitEditor.java:209)
	at 
org.eclipse.jdt.internal.ui.javaeditor.CompilationUnitEditor.doSave(CompilationU
nitEditor.java:257)
	at org.eclipse.ui.internal.EditorManager$9.run(EditorManager.java:776)
	at 
org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:29
6)
	at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:249)
	at 
org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:3
35)
	at 
org.eclipse.ui.internal.EditorManager.runProgressMonitorOperation(EditorManager.
java:634)
	at 
org.eclipse.ui.internal.EditorManager.saveEditor(EditorManager.java:781)
	at 
org.eclipse.ui.internal.WorkbenchPage.saveEditor(WorkbenchPage.java:1173)
	at org.eclipse.ui.internal.SaveAction.run(SaveAction.java:31)
	at org.eclipse.jface.action.Action.runWithEvent(Action.java:451)
	at 
org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionCont
ributionItem.java:407)
	at 
org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionContribu
tionItem.java(Compiled Code))
	at 
org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(Actio
nContributionItem.java(Compiled Code))
	at 
org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(Actio
nContributionItem.java(Compiled Code))
	at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java(Compiled 
Code))
	at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java(Compiled 
Code))
	at 
org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java(Compiled Code))
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java(Compiled 
Code))
	at 
org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java(Compiled Code))
	at org.eclipse.ui.internal.Workbench.run(Workbench.java:658)
	at 
org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:82
0)
	at org.eclipse.core.boot.BootLoader.run(BootLoader.java:285)
	at java.lang.reflect.Method.invoke(Native Method)
	at org.eclipse.core.launcher.Main.basicRun(Main.java:151)
	at org.eclipse.core.launcher.Main.run(Main.java:502)
	at org.eclipse.core.launcher.Main.main(Main.java:362)
	4 org.eclipse.jdt.core 969 build does not exist.
Comment 1 Philipe Mulet CLA 2001-10-29 06:24:54 EST
Are you sure you weren't running 204 instead ? There was some circumstances 
where the package view did not refresh properly when changes happened to edited 
files. As a consequence, it would keep stale handles, which would behave 
defensively by throwing a NotPresentException.

This was fixed in 205 and better in the Java UI. Have you seen it since then ?
Comment 2 John Arthorne CLA 2001-10-29 09:15:53 EST
No, I have only seen it that one time.  It's possible I'm mistaken about the 
build number, but I don't remember ever installing build 204.  I think I went 
straight from 203 to 20011018 (aka 205).
Comment 3 Philipe Mulet CLA 2002-02-12 13:36:07 EST
Jerome - I think this one is obsolete ?
Comment 4 Jerome Lanneluc CLA 2002-02-13 11:06:17 EST
Yes, delta processing has been rewritten since then, thus the UI would have 
been notified of the removal of the method 'build'.
Closing.