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 98769 - Deleted WSDL content is not removed from Navigator window
Summary: Deleted WSDL content is not removed from Navigator window
Status: CLOSED DUPLICATE of bug 104229
Alias: None
Product: platform
Classification: Unclassified
Component: Navigator (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: David Simonek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-23 10:34 UTC by srinivaschintalapati
Modified: 2008-12-22 11:00 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description srinivaschintalapati 2007-03-23 10:34:05 UTC
Steps to Reproduce:
1) Create BPEL Module and Create a wsdl docucument for say FileBC
2) Delete the wsdl.  [be sure that only WSDL is present in the entire module-
process folder i.e. no bpel process is created ]
3) Navigator Window having the wsdl view does not get cleared.

Observation: 
1) multiple WSDL's or any other file(like bpel process) having a Module works 
fine.  But Module having single WSDL will not be cleared in the Navigator 
window.
2) This is the same case with a single BPEL process i.e. when BPEL process is 
deleted, Navigator window doesnt get cleaned.

Build Details:

NetBeans IDE Dev (Build 200703191900)
1.6.0; Java HotSpot(TM) Client VM 1.6.0-b105
Windows XP version 5.1 running on x86
en_US (nb); Cp1252
Comment 1 Venkat Chellasamy 2007-04-09 23:02:03 UTC
This is a general NetBeans issue. NetBeans doesn't have the so-called
Perspective support in Eclipse. 

To reproduce this problem in NetBeans IDE:

1. Create a new Java Project, 
2. Delte the Java Project,
3. The Navigator window still shows the class structure of the deleted Java class.

Comment 2 David Simonek 2007-06-21 10:08:36 UTC
Duplicate or 104229, which is now fixed. Sorry I didn't notice this older bug so I did duplication against time, but
it's fixed, that matters.

*** This issue has been marked as a duplicate of 104229 ***