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.
Summary: | Deadlock between Module-Actions and EQ | ||
---|---|---|---|
Product: | java | Reporter: | pzajac <pzajac> |
Component: | Beans | Assignee: | issues@java <issues> |
Status: | VERIFIED FIXED | ||
Severity: | blocker | Keywords: | RANDOM, THREAD |
Priority: | P2 | ||
Version: | 3.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | thread dump |
Description
pzajac
2003-11-07 14:43:11 UTC
Created attachment 12089 [details]
thread dump
Not ModuleActions, but somebody from the stack should put the code into AWT Thread. I don't know who, passing to first candidate (AddPropertyAction). Fixed as part of issue #35755. *** This issue has been marked as a duplicate of 35755 *** I doubt it. Issue #35755 did not change the default behavior of any actions except those listed; you have to override asynchronous() to return false to make it take effect. beans.AddPropertyAction does not yet do this from what I can see. Anyway #35755 was fixed well before this issue was even opened. OK, Jesse you are right. It was fixed in ElementNode.ElementListener.propertyChange(), which runs in event thread. it looks fine |