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 7615 - Two PropertyChangeEvents are fired instead of one
Summary: Two PropertyChangeEvents are fired instead of one
Status: CLOSED FIXED
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-09-12 10:33 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-09-12 10:33:11 UTC 
For example:

MethodElement me = clazz.getMethod(...

me.setModifiers(...

In this case two PropertyChangeEvents are fired. The first with "modifiers" as
propertyName. The second one with "body". The same problem is with calling
other setters (setName(), setReturn()...) and even with other Elements
(FieldElement...)
Comment 1 Jan Becicka 2000-09-12 10:39:59 UTC 
[1098]
Comment 2 Svata Dedic 2000-09-25 11:25:59 UTC 
a) FieldElements should *not* fire PROP_BODY property change event since they
have PROP_INITIALIZER for the same thing. The event firing will be disabled for
them
b) constructor, initializer and method elements keep hash of the body for fast
change detection; the old and new hashes weren't compared well.
Comment 3 Jan Becicka 2000-11-03 16:24:59 UTC 
[1137], [dev-62]
Seems to be fixed, except this case:
If InitializerElement.setStatic() is called, "static" and "body"
PropertyChangeEvents are fired, but only "static" should.
Comment 4 Svata Dedic 2001-04-18 16:04:52 UTC 
blah
Comment 5 Svata Dedic 2001-04-18 16:05:25 UTC 
Should be fixed in current release-3.2/dev builds
Comment 6 Jan Becicka 2001-04-27 15:15:02 UTC 
[NB3.2.38] Verified
Comment 7 Jan Chalupa 2001-05-05 23:27:07 UTC 
Target milestone -> 3.2
Comment 8 Quality Engineering 2003-07-01 13:17:43 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.