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 13805

Summary:	ObjectBrowser doesn't show properties of Objects and Members
Product:	java	Reporter:	Jan Chalupa <jchalupa>
Component:	Unsupported	Assignee:	Petr Suchomel <psuchomel>
Status:	RESOLVED WONTFIX
Severity:	blocker	CC:	erider, psuchomel, rdankanin
Priority:	P3
Version:	3.x
Hardware:	All
OS:	All
Issue Type:	DEFECT	Exception Reporter:
Attachments:	Patch for JDK1.4

Description Jan Chalupa 2001-07-23 12:20:41 UTC

Originally reported by ethan.rider@sun.com

Using JDK1.4 beta-refresh build 72 and NetBeans 3.2 the IDE will not show 
properties of objects and their members in the Object Browser.  When an Object 
or a Member with properties is selected, the Properties Window content is not 
updated with appropriate information.

Comment 1 Petr Suchomel 2001-07-23 15:50:41 UTC

Problem is that Nodes in Object Browser seem not to be Nodes. There 
are no actions on nodes, nodes on enable(Nodes[] nodes) gives 
node.length == 0.

Comment 2 Petr Suchomel 2001-07-24 16:08:37 UTC

Trying to debug problem I found that Node[] getActivatedNodes returns 
node.length == 0, like no node is activated. This bugs leads to have 
no properties shown and action available but disabled on nodes.

Comment 3 Robert Dankanin 2001-07-25 10:04:01 UTC

Adding JDK_1.4 keyword.
Reproduced also under NB 3.3 [Main trunk build #200107240100]
Reassigning to new owner.

Comment 4 David Strupl 2001-07-25 15:24:12 UTC

Marek, have you heard about any problems with
getActivatedNodes on JDK1.4 build 72? Reassigning to you as
it seems as problem of window system.

Comment 5 mslama 2001-07-26 19:21:06 UTC

The problem is that objectbrowser does not call
TopComponent.setActivatedNodes(). It seems to me that problem is with
focus because variable isFacused (yes really isFacused :)) in ExplorerBean
is always false under JDK 1.4.0 b 73. (I checked the same with 1.3.1
and this variable is at least sometimes true so it works correctly on
1.3.1.) So I reassign back to objectbrowser. We can look at this focus
problem together if necessary we solved some focus problems in window
system already (not easy thing).

More details:
Here is piece of dump stack, problem is that on 1.4.0 in ExplorerBean
call of TopComponent.setActivatedNodes from
ExplorerBean$1.propertyChange is not performed. 

at
org.netbeans.core.windows.RegistryImpl.selectedNodesChanged(RegistryImpl.java:249)
        at
org.netbeans.core.windows.WindowManagerImpl$TopComponentManager.setActivatedNodes(WindowManagerImpl.j
ava:1233)
        at
org.openide.windows.TopComponent.setActivatedNodes(TopComponent.java:162)
        at
org.netbeans.modules.objectbrowser.ExplorerBean$1.propertyChange(ExplorerBean.java:144)
        at
java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:152)
        at
org.openide.explorer.ExplorerManager.setSelectedNodes(ExplorerManager.java:193)

Comment 6 mslama 2001-07-27 13:21:06 UTC

Assign to psuchomel

Comment 7 support 2001-08-01 12:21:23 UTC

Created attachment 2028 [details]
Patch for JDK1.4

Comment 8 Jan Chalupa 2001-11-27 15:27:37 UTC

Target milestone -> 3.3.1.

Comment 9 Marek Grummich 2002-07-22 11:12:10 UTC

Set target milestone to TBD

Comment 10 Jan Chalupa 2005-04-10 16:46:44 UTC

Object browser is dead. No plans to work on this issue anymore. Closing as WONTFIX.