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 53750 - Tables show null when Customizer shown
Summary: Tables show null when Customizer shown
Status: RESOLVED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Explorer (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: Stanislav Aubrecht
URL:
Keywords:
: 67969 75227 79787 81826 93205 95580 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-01-20 14:21 UTC by Milan Kubec
Modified: 2008-12-22 10:51 UTC (History)
6 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
screenshot (18.24 KB, image/png)
2005-01-20 14:37 UTC, Milan Kubec 		Details
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 Milan Kubec 2005-01-20 14:21:31 UTC 
[dev-200501191900, JDK 1.5.0_02]

See screenshot, it shows that if user uses very
usefull feature, I mean clicks '...' to display
the same value that is in the table row then the
value changes to 'null'. This applies for any
value displayer in debugger views (in Watches,
Threads, Sessions, Local Variables)
Comment 1 Milan Kubec 2005-01-20 14:37:09 UTC 
Created attachment 19817 [details]
screenshot
Comment 2 Jan Jancura 2005-01-20 20:28:45 UTC 
Reproducible. Looks like TTV bug.
Comment 3 Jan Jancura 2005-04-13 09:28:29 UTC 
No chance to fix it in 4.1.
Comment 4 Martin Entlicher 2005-08-16 15:46:59 UTC 
I can reproduce this only in Sessions and Threads views.
Comment 5 Martin Entlicher 2005-08-16 16:16:05 UTC 
This looks like a bug in property sheet implementation.
When the editor is invoked, the value is changed to null. But when the editor is
closed, the original value is put there, even though it does not ask the model
for it.
Comment 6 Martin Krauskopf 2005-09-06 16:55:10 UTC 
I don't know debugger code but property sheet implementation looks good to me.
Probably bad usage on the side of the debugger (it works ok on all other
places). If you feel opposite please tell me more detail about your implementation.
Comment 7 Martin Entlicher 2005-12-12 18:10:43 UTC 
This can be reproduced only in "State" column of Sessions and Threads view.

It looks that the "null" is temporarily displayed iff htmlDisplayName attribute
is null. This is unexpected, because that attribute should be ignored when null.

During debugging it looks like there's some problem in RendererFactory - the
StringRenderer.reset() method sets the "null" string from editor.getAsText().
This looks suspicious - the editor is likely not initialized at that time.

Please reevaluate...
Comment 8 Marian Mirilovic 2006-08-14 08:29:12 UTC 
*** Issue 75227 has been marked as a duplicate of this issue. ***
Comment 9 Marian Mirilovic 2006-08-14 08:30:21 UTC 
*** Issue 67969 has been marked as a duplicate of this issue. ***
Comment 10 Marian Mirilovic 2006-08-14 08:31:03 UTC 
*** Issue 81826 has been marked as a duplicate of this issue. ***
Comment 11 Alexander Zgursky 2006-09-07 14:54:17 UTC 
I can still reproduce this bug in 5.5 beta. Is there someone working on it?
According to mkrauskopf's comment the problem might be in the Debugger Core
implementation. Please evaluate it and consider reassigning to Debugger Core.
Comment 12 Alexander Zgursky 2006-09-07 14:55:43 UTC 
*** Issue 79787 has been marked as a duplicate of this issue. ***
Comment 13 Alexander Pepin 2006-10-18 13:45:51 UTC 
Please pay your attention to this bug. Somehow it fell out from the scope but it
still exists in NB 5.5. Sometimes all values disappears from the table when an
editor window is opened for one of them.
Comment 14 Martin Entlicher 2007-02-14 16:47:03 UTC 
*** Issue 95580 has been marked as a duplicate of this issue. ***
Comment 15 Kirill Sorokin 2008-02-15 07:48:49 UTC 
*** Issue 93205 has been marked as a duplicate of this issue. ***
Comment 16 Kirill Sorokin 2008-02-15 07:51:36 UTC 
BPEL Debugger views seem to be seriously affected by this, so I'm raising the priority.

If there is no problem with the API, then please, show us how to "cook" it properly. :-)
Comment 17 Kirill Sorokin 2008-02-15 07:52:43 UTC 
Remove the stale dependency.
Comment 18 Stanislav Aubrecht 2008-02-19 16:16:49 UTC 
this issue is a side-effect of fix for #52179
Comment 19 Stanislav Aubrecht 2008-02-27 16:05:32 UTC 
fixed

dc8c162e7dca