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 7905 - JavaConnections: TYPE_CLESSES_CHANGE fired instead of TYPE_CLESSES_CHANGE | TYPE_INITIALIZERS_CHANGE
Summary: JavaConnections: TYPE_CLESSES_CHANGE fired instead of TYPE_CLESSES_CHANGE | T...
Status: CLOSED WONTFIX
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P4 normal (vote)
Assignee: issues@java
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2000-10-13 11:54 UTC by Jan Becicka
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Becicka 2000-10-13 11:54:53 UTC 
[1120]
after invoking initializerElement.setBody() or initializerElement.setStatic(),
JavaConnections.TYPE_CLASSES_CHANGE is fired, but the right mask should be
JavaConnections.TYPE_CLASSES_CHANGE | JavaConnections.TYPE_INITIALIZERS_CHANGE.
Isn't it?
Comment 1 Svata Dedic 2000-10-13 17:19:59 UTC 
TYPE_CLASSES_CHANGE should be fired _only_ if class' own properties has changed.
Changes in sub-elements (add/remove/change) do not affect the class properties,
so CLASSES_CHANGE will not be fired if changing/adding/removing
field/method/initializer.
As for setBody() reports - body contents changes are _not_ fired as Java
Connection events.
Comment 2 Jan Becicka 2000-11-03 15:41:59 UTC 
*** This bug has been marked as a duplicate of 7902 ***
Comment 3 Quality Engineering 2003-07-01 13:12:37 UTC 
Resolved for 3.3.x or earlier, no new info since then -> closing.
Comment 4 Quality Engineering 2003-07-01 13:20:27 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.