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: | JavaConnections.TYPE_CLASSES_CHANGE | JavaConnections.TYPE_CONSTRUCTORS_CHANGE are fired, but why? | ||
---|---|---|---|
Product: | java | Reporter: | Jan Becicka <jbecicka> |
Component: | Unsupported | Assignee: | issues@java <issues> |
Status: | CLOSED INVALID | ||
Severity: | normal | ||
Priority: | P4 | ||
Version: | 3.x | ||
Hardware: | PC | ||
OS: | Windows ME/2000 | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Jan Becicka
2000-10-16 13:09:19 UTC
It seems that the changes are recorded although no one is really interested in them. After you register for javaconnections, diff from the old stored state is fired. It seems that the behaviour you are experiencing is a side effects of delayed resolution of identifiers in the source. Those events are fired after reparse of the source text is done. Your listener is registered before the background reparse scheduled from within createFromTemplate() completes. Then it appears as the code has to notify about changes, b/c there IS a listener. x From my point of view, the behaviour is OK. You simply attach the listener at wrong time - the implementation decides to fire change events after you attach it. To prevent this behaviour, you can call prepare() on the source and wait for the background parsing to complete. Then any delayed actions (like ident resolution + dependendings) are already scheduled or executed so you should not get those events. Resolved for 3.3.x or earlier, no new info since then -> closing. Resolved for 3.4.x or earlier, no new info since then -> closing. |