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 40886 - inconsistent behaviour found in sun-web Open/Edit menu
Summary: inconsistent behaviour found in sun-web Open/Edit menu
Status: RESOLVED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Infrastructure (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: Pavel Buzek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-09 22:41 UTC by davisn
Modified: 2004-09-21 19:44 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 davisn 2004-03-09 22:41:27 UTC 
Build used:
    Netbean & plugin: 03/08

STEPS TO REPRODUCE:
1. Install Netbean and plugin
2. Start Netbean IDE
3. Create a Web Module
4. Create a JSP file (eg. index.jsp)
5. Right-click at the index.jsp and select Open menu 
6. Right-click at the sun-web node and select Edit
menu
7. Right-click at the sun-web node again and
select Open menu

BUG:
    The Open menu didn't come up
    
EXPECTING RESULT:
    Either the Open editor should come up or the
Open menu should be greyed out since sun-web is
already in the Edit mode
Comment 1 Pavel Buzek 2004-03-10 17:04:28 UTC 
The expected behavior is that only one of Edit or Open editors can be
open. Did you restart the IDE between steps 6 and 7? In that case it
would be a duplicate of #40534.
Comment 2 Pavel Buzek 2004-08-06 21:51:09 UTC 
with tomcat5 it allows to Edit and Open the same file; these actions
should be mutually exclusive
Comment 3 Pavel Buzek 2004-09-21 19:44:54 UTC 
Fixed by Martin Adamek who separated the implementation of open cookie
from the data object. This worked in 3.6 but stopped working with the
Filter node that uses lookup as a primary way to obtain cookies and of
course the DataObject is in lookup of a DataNode. Thanks for the fix!