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 92309 - Renaming of watched expression doesn't take effect immediately
Summary: Renaming of watched expression doesn't take effect immediately
Status: VERIFIED FIXED
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 6.x
Hardware: All All
: P4 blocker (vote)
Assignee: Martin Entlicher
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-11 12:46 UTC by novakm
Modified: 2007-03-28 10:23 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 novakm 2007-01-11 12:46:40 UTC 
Assuming debug session is not running yet.
Steps to reproduce:
1) Invoke Run | New Watch... and write anything, eg. "i"
2) In Watches tab, select the watched variable i and double click it (or invoke
Properties from its context menu)
3) Rename the variable, for example to "j"
result: "i" is still displayed

However, when the debug session starts, the correct name is displayed. If you
rename the variable during debug, correctly renamed name is displayed immediately.

-----
NetBeans IDE Dev (Build 200701101900)
1.5.0_11; Java HotSpot(TM) Client VM 1.5.0_11-b03
Windows XP version 5.1 running on x86
cs_CZ (nb); Cp1250
-----
Comment 1 Martin Entlicher 2007-01-11 13:43:14 UTC 
This is likely because of the following exception, which is thrown into the console.

java.lang.IllegalStateException: Warning - the node "#value"
[org.netbeans.modules.viewmodel.TreeModelNode] is trying to fire the property
expression which is not included in its property sets. This is illegal. See IZ
#31413 for details.
        at org.openide.nodes.Node.firePropertyChange(Node.java:911)
        at
org.netbeans.modules.viewmodel.TreeModelNode.refreshColumn(TreeModelNode.java:373)
        at
org.netbeans.modules.viewmodel.TreeModelRoot$1.run(TreeModelRoot.java:100)
        at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
        at java.awt.EventQueue.dispatchEvent(EventQueue.java:597)
        at
java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:273)
        at
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:183)
        at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:173)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:168)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:160)
        at java.awt.EventDispatchThread.run(EventDispatchThread.java:121)
Comment 2 ehucka 2007-03-16 13:26:00 UTC 
I think this issue downgrade credibility of debugger. New users will not trust
in debugger which does not even change name of watches correctly. :)
Comment 3 Martin Entlicher 2007-03-21 12:15:48 UTC 
Well, there are many other issues, which downgrade credibility of debugger ;-)

So, do you propose to increase the priority of this issue?
Comment 4 ehucka 2007-03-21 13:52:44 UTC 
Maybe. Such small things make the product worthy. :)
Comment 5 Martin Entlicher 2007-03-21 14:52:06 UTC 
O.K. The problem is identified, a bad property name is fired.
Comment 6 Martin Entlicher 2007-03-21 14:55:51 UTC 
Fixed in trunk:

/shared/data/ccvs/repository/debuggercore/src/org/netbeans/modules/debugger/ui/models/WatchesTreeModel.java,v
 <--  WatchesTreeModel.java
new revision: 1.11; previous revision: 1.10
Comment 7 novakm 2007-03-28 10:23:26 UTC 
Verified in Build 200703272330.