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 27177 - Sometime "Server And External Tool Settings" appears without spaces
Summary: Sometime "Server And External Tool Settings" appears without spaces
Status: VERIFIED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Nodes (show other bugs)
Version: 3.x
Hardware: Sun Solaris
: P4 blocker (vote)
Assignee: Petr Nejedly
URL:
Keywords: RANDOM
: 33543 (view as bug list)
Depends on:
Blocks:
 
Reported: 2002-09-10 15:35 UTC by Oleg Khokhlov
Modified: 2008-12-23 11:37 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
S1S 4 update 1 EE build 030106. W2K, JDK 1.4.1 (55.80 KB, image/jpeg)
2003-01-09 13:39 UTC, Oleg Khokhlov
Details
Call stack for setDisplayName() (2.00 KB, text/plain)
2003-02-26 13:46 UTC, mslama
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Oleg Khokhlov 2002-09-10 15:35:45 UTC
'Server And External Tool Settings' in
"Tools->Options->IDE Configuration->Server And
External Tool Settings" can appear without spaces
sometime (as 'ServerAndExternalToolSettings').
It prevents running of HTTP server related
automated tests (they use "Tools->Options->IDE
Configuration->Server And External Tool
Settings->HTTP Server" settings)

Solaris 9, JDK 1.4.0_02
S1S 4 update 1 build 020905
Comment 1 Alexei Mokeev 2002-09-13 13:56:05 UTC
Problem with "ServerAndExternalToolSettings" without of spaces
reproduced for me too(not each time, but often)
However looks like this is common problem, because sometimes spaces
missed from other messages. For example
when try to rename some node via popup menu: In "Rename" dialog text
field named "NewName:" instead of "New Name".
Such problems causes many failures of automated tests.

Comment 2 Marian Mirilovic 2002-11-13 15:32:33 UTC
changed owner Dafe -> Peter Z.
Comment 3 Peter Zavadsky 2002-12-04 17:41:07 UTC
Marian please could you have a look at it and let me know whether it
is reproducible? I don't see it in NB.
Comment 4 Marian Mirilovic 2002-12-05 09:13:11 UTC
I cannot reproduce it.

Oleg:
Are you sure that tests fail because no spaces in the node name?

Alexei:
Please be more exact, what does it mean "some node" ?
Comment 5 Alexei Mokeev 2002-12-05 09:31:23 UTC
Some node(node on filesystems tab of explorer) it is some jsp, servlet
on html file.
Comment 6 Marian Mirilovic 2002-12-06 17:58:07 UTC
reassigne to Marek, new owner of ui subcomponents
Comment 7 Oleg Khokhlov 2003-01-09 13:39:20 UTC
Created attachment 8500 [details]
S1S 4 update 1 EE build 030106. W2K, JDK 1.4.1
Comment 8 mslama 2003-02-26 13:41:00 UTC
It happens in current NB dev build too. I found that
LookupNode.setDisplayName() is called with node name not with
localized values. I tried to modify localized bundle for this node but
no change. Reassign to nodes.
Comment 9 mslama 2003-02-26 13:44:03 UTC
I assume that node display name should be taken from localized bundle.
Am I right?
Comment 10 mslama 2003-02-26 13:46:30 UTC
Created attachment 9165 [details]
Call stack for setDisplayName()
Comment 11 Alexei Mokeev 2003-03-19 13:34:02 UTC
Reproduced with S1S 5 build 030312_1
Comment 12 mslama 2003-05-13 16:40:46 UTC
*** Issue 33543 has been marked as a duplicate of this issue. ***
Comment 13 Petr Nejedly 2004-01-09 09:45:17 UTC
Taking over the node bugs from phrebejk.
Comment 14 Petr Nejedly 2004-03-02 11:48:33 UTC
My findings:

Generally, DataNode is broken "a bit":
it calls setDisplayName() with base name of the file (not annotated =>
not localized), which fires PCE with this name as new value.
if you call getDisplayName, you'll get correct result (annotated, as
getDN calls super.getDN and then annotates it).

But if you take the value from the PCE, you'll have the bare name....
Comment 15 Petr Nejedly 2005-03-16 14:18:23 UTC
Sorry, but it seems this can't be fixed correctly while it is very easy to
workaround it on API client side (don't depend on evt.getNewValue()).

Comment 16 mslama 2005-03-16 14:37:49 UTC
Seems to be fixed. All known nodes already use getDisplayName(). If you see any
other occurrence of this issue in dev build please reopen with info about exact
location in UI so we are able to find responsible node. Thanks.
Comment 17 mslama 2005-03-16 14:38:15 UTC
Fixed already.
Comment 18 Marian Mirilovic 2005-12-20 15:58:07 UTC
This issue was solved long time ago. Because nobody has reopened it neither
added comments, we are verifying/closing it now. 
If you are still able to reproduce the problem, please reopen. Thanks in advance.