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 32616 - Incorrect double click action for 'Sun ONE Application server 7' node
Summary: Incorrect double click action for 'Sun ONE Application server 7' node
Status: CLOSED INVALID
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 3.x
Hardware: Sun SunOS
: P2 blocker (vote)
Assignee: issues@platform
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-04-04 08:03 UTC by vgorr
Modified: 2008-12-23 11:53 UTC (History)
2 users (show)

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 vgorr 2003-04-04 08:03:02 UTC 
To reproduce this issue you need to run the
following steps:
o select the Runtime workspace for Explorer;
o double click on Server Registry node.
  It is successfully expanded;
o double click on Installed Servers node.
  It is successfully expanded;
o for now try to double click on SunONE
Application Server 7 node.
  This node IS NOT EXPANDED. The Property window
is opened instead.
  I suppose this action is incorrectly performed.
Comment 1 Marian Mirilovic 2003-04-04 08:38:01 UTC 
Vladimir, it isn't a Core/Openide issue. 

If you double click some node default action is runned. The default
action is set by Node "owner/creator".

 I know nothing about 'Sun ONE Application server 7' node, but it's
owner is responsible for the default action definition. So please file
bug into BugTraq against (I don't know Application server or something
else) and close this one with the bug number as INVALID, thanks in
advance.
Comment 2 vgorr 2003-04-04 08:43:00 UTC 
Absolutely agree with you, Marian. It's my fault :-(.
Sorry for this misunderstanding. I'll re-open this issue for bugtraq.
Comment 3 vgorr 2003-04-04 09:33:18 UTC 
This issue has been re-opened into bugtraq.
Comment 4 Marian Mirilovic 2003-04-04 09:40:51 UTC 
Only for registry bug number ? Thanks again.
Comment 5 vgorr 2003-04-04 11:58:38 UTC 
bugtraq id for this issue is 4842820.