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 32470

Summary:	Selecting a RMI registry node ends up having 2 activated nodes
Product:	platform	Reporter:	Jan Kovar <jkovar>
Component:	Window System	Assignee:	Jaroslav Tulach <jtulach>
Status:	VERIFIED FIXED
Severity:	blocker	CC:	jglick, phrebejk
Priority:	P3
Version:	3.x
Hardware:	All
OS:	All
Issue Type:	DEFECT	Exception Reporter:
Attachments:	Test that is reproducing the problem Fix (includes API change) and a test JAR patch for version 3.5

Description Jan Kovar 2003-03-28 15:49:41 UTC

After fixing bug 
<http://www.netbeans.org/issues/show_bug.cgi?id=31743> I 
do not know a reproducible case.

Anyway when you select a RMI Registry node in Runtime tab 
the CookieAction.enable method is getting 2 nodes as 
activatedNodes. One is RMIRegistryNode and one is its 
FilterNode.
I think there should be only one activatedNode as only one 
node is selected in the IDE.

Comment 1 Jaroslav Tulach 2003-03-31 12:10:21 UTC

Ok, let's look for what is going on.

Comment 2 Jaroslav Tulach 2003-04-03 09:42:38 UTC

Created attachment 9677 [details]
Test that is reproducing the problem

Comment 3 Jaroslav Tulach 2003-04-03 13:24:30 UTC

Created attachment 9678 [details]
Fix (includes API change) and a test

Comment 4 Jaroslav Tulach 2003-04-03 13:27:07 UTC

Created attachment 9679 [details]
JAR patch for version 3.5

Comment 5 Jaroslav Tulach 2003-04-03 13:29:36 UTC

Jan, can you please verify that the attached patch solves the problem
for the old version of RMI module?

Comment 6 Jan Kovar 2003-04-04 08:54:16 UTC

Verified in Nevada build 030323.

Comment 7 Marian Mirilovic 2003-04-04 15:51:28 UTC

This issue is not planned to be fixed for 3.5, changing TM = 4.0

Comment 8 Jaroslav Tulach 2003-04-07 12:54:29 UTC

Guys can you check this diff? I think I'd apply that just for main
trunk as the conditions for reproducing the bug are really obscure and
it is better not to tease 3.5. Ok?

Comment 9 Jaroslav Tulach 2003-04-07 15:20:15 UTC

Checking in api/doc/changes/apichanges.xml;
/cvs/openide/api/doc/changes/apichanges.xml,v  <--  apichanges.xml
new revision: 1.152; previous revision: 1.151
done
Processing log script arguments...
More commits to come...
Checking in src/org/openide/nodes/FilterNode.java;
/cvs/openide/src/org/openide/nodes/FilterNode.java,v  <--  FilterNode.java
new revision: 1.79; previous revision: 1.78
done
Processing log script arguments...
More commits to come...
Checking in src/org/openide/windows/DefaultTopComponentLookup.java;
/cvs/openide/src/org/openide/windows/DefaultTopComponentLookup.java,v
 <--  DefaultTopComponentLookup.java
new revision: 1.12; previous revision: 1.11
done
Processing log script arguments...
More commits to come...
Checking in
test/unit/src/org/openide/windows/TopComponentGetLookupTest.java;
/cvs/openide/test/unit/src/org/openide/windows/TopComponentGetLookupTest.java,v
 <--  TopComponentGetLookupTest.java
new revision: 1.11; previous revision: 1.10
done
Processing log script arguments...
More commits to come...
Checking in openide-spec-vers.properties;
/cvs/openide/openide-spec-vers.properties,v  <-- 
openide-spec-vers.properties
new revision: 1.112; previous revision: 1.111
done

openide/loaders/src/org/openide/loaders/InstanceDataObject.java, rev. 1.3

Comment 10 Marian Mirilovic 2004-03-17 15:20:45 UTC

fixed lon time ago - verified