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 10066 - Bugs in JavaConnections
Summary: Bugs in JavaConnections
Status: CLOSED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: issues@java
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-03-07 18:46 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 2001-03-07 18:46:16 UTC 
[dev-139]
1. ClassElement.addMethods fires 2 JavaConnections: TYPE_METHODS_ADD and 
TYPE_METHODS_CHANGE, but only TYPE_METHODS_ADD shoud be fired.
2. ClassElement.addClass does not fire TYPE_CLASSES_ADD
3. ClassElement.addInitializer does not fire TYPE_INITIALIZERS_ADD
4. ClassElement.removeInitializer does not fire TYPE_INITIALIZERS_REMOVE 
5. ClassElement.removeConstructors does not fire TYPE_CONSTRUCTORS_REMOVE
6. ClassElement.removeInterfaces does not fire TYPE_CLASSES_REMOVE
Comment 1 Jan Becicka 2001-03-09 11:13:01 UTC 
JavaConnections are important for other modules. -> I'm rising priority.
Comment 2 Jan Chalupa 2001-03-12 10:46:29 UTC 
Version: 'Dev' -> 3.2
Comment 3 Svata Dedic 2001-03-16 18:48:55 UTC 
Fixed in release-3.2, dev-trunk.
Comment 4 Jan Chalupa 2001-05-05 23:24:37 UTC 
Target milestone -> 3.2
Comment 5 Jan Becicka 2001-06-18 12:39:30 UTC 
ClassElement.addMethods still fires 2 JavaConnections: TYPE_METHODS_ADD and 
TYPE_METHODS_CHANGE, but only TYPE_METHODS_ADD shoud be fired.
Bug is almost fixed -> changing priority.
Comment 6 Tomas Hurka 2001-06-22 14:02:59 UTC 
fixed in trunk
Comment 7 Tomas Hurka 2001-06-22 18:41:04 UTC 
/cvs/java/src/org/netbeans/modules/java/model/CallableImpl.java,v  <-- 
CallableImpl.java
new revision: 1.12; previous revision: 1.11
done
/cvs/java/src/org/netbeans/modules/java/codesync/ModelEventAdapter.java,v  <-- 
ModelEventAdapter.java
new revision: 1.9; previous revision: 1.8
done
Comment 8 Jan Becicka 2001-06-27 17:27:34 UTC 
ClassElement.addMethods still "sometimes" fires 2 JavaConnections: 
TYPE_METHODS_ADD and 
TYPE_METHODS_CHANGE, but only TYPE_METHODS_ADD shoud be fired.
Comment 9 Jan Becicka 2001-10-12 14:26:31 UTC 
And one more issue:
ClassElement.addInterface fires TYPE_CLASSES_CHANGE, but 
TYPE_CLASSES_ADD should be fired.
ClassElement.removeInterface fires TYPE_CLASSES_CHANGE, but 
TYPE_CLASSES_REMOVE should be fired.
Comment 10 Svata Dedic 2001-11-22 16:41:23 UTC 
I'm postponing the solution:

From the conversation with the reporter:
> The root 
> of this bug lies in insufficient data distributed in 
JavaConnection 
> events. The module uses similar events internally; I can extend 
the 
> synchronized part so that the JavaConnection event source gets the 
> events in the correct order and merges them correctly; however the 
> client will be always outside the synchronized section (as a 
prevention 
> from deadlocks) and will always receive only partial data.
> So - your test will stop to fail, but the real users will still 
receive 
> only partially useful information.
Comment 11 Jan Becicka 2002-01-11 16:57:35 UTC 
Reopening
Comment 12 Jan Becicka 2002-01-11 16:58:19 UTC 
Already fixed
Comment 13 Jan Becicka 2002-01-11 17:00:27 UTC 
Verified
Comment 14 Quality Engineering 2003-07-01 13:20:04 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.