This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 36605 - ISE thrown when doing compilation
Summary: ISE thrown when doing compilation
Status: VERIFIED DUPLICATE of bug 36681
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 3.x
Hardware: All All
: P2 blocker (vote)
Assignee: Jesse Glick
Keywords: THREAD
Depends on:
Reported: 2003-10-15 11:21 UTC by Milan Kubec
Modified: 2008-12-22 20:57 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

exc stack trace (3.57 KB, text/plain)
2003-10-15 11:22 UTC, Milan Kubec

Note You need to log in before you can comment on or make changes to this bug.
Description Milan Kubec 2003-10-15 11:21:56 UTC
IllegalStateException is thrown when doing
compilation while editor has focus. 

Steps to reproduce:
1) Open java file in editor
2) Modify that file
3) Press F9

Exception is thrown. Compilation is succesfully
Comment 1 Milan Kubec 2003-10-15 11:22:20 UTC
Created attachment 11864 [details]
exc stack trace
Comment 2 Milan Kubec 2003-10-17 10:39:33 UTC
This is very annoying bug. I forgot to mention that the exception is
printed to Output window and thus user could think that the problem
can be in compiled code. 

Could it be at least evaluated?
Comment 3 pzajac 2003-10-20 10:00:40 UTC
reassigned to openide/awt
Comment 4 _ tboudreau 2003-10-22 10:14:42 UTC
Reassign to actions.
Comment 5 _ tboudreau 2003-10-22 10:16:40 UTC
Probably SharedClassObject could replane its property changes into the
AWT thread.
Comment 6 Peter Zavadsky 2003-10-22 10:27:09 UTC
For sure not SharedClassObject has to do that. Also action itself not. 

The question is which part from the stack trace has to be called from
AWT thread first, then its client has to do that. 

Actions has to be called from AWT thread, so the changle listener is
the last candidate, but I'd like to now whether also the nodes should
be manipulated also from AWT thread, then somebody else is responsible
fot that.
Comment 7 Jaroslav Tulach 2003-10-22 13:27:06 UTC
Related to changes in threading model in actions.
Comment 8 Jesse Glick 2003-10-22 18:07:48 UTC

*** This issue has been marked as a duplicate of 36681 ***
Comment 9 Milan Kubec 2003-10-23 09:33:39 UTC