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 24687 - During opening new project some wstcref files might not be stored
Summary: During opening new project some wstcref files might not be stored
Status: CLOSED WORKSFORME
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 3.x
Hardware: PC Solaris
: P3 blocker (vote)
Assignee: Peter Zavadsky
URL:
Keywords:
Depends on: 23065
Blocks:
  Show dependency tree
 
Reported: 2002-06-12 12:25 UTC by mslama
Modified: 2008-12-23 09:40 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 mslama 2002-06-12 12:25:42 UTC
It is caused by issue #23065. DataObject.find()
can sometimes return invalid DO when its primary
file was just created. It often happens on
Solaris, JDK 1.4.0-b92 when new project is opened.
This issue was also part of issue #24586. After
discussion with Dafe we decided not to remove
check of DO validity in ModeData when files
wstcref because we could hide some other problems.

Steps to reproduce:
1.Open IDE with empty user dir.
2.Open any txt file in Source Editor (README.txt)
3.Open new project. Sometimes
FileNotFoundException is logged to ide.log and to
console for file README.wstcref. (We check if FO
and DO is valid before we create instance of top
component in TCRefImpl.getTopComponent().

Result is that if you switch back to original
project not saved top component references will
not be reopened.
Comment 1 mslama 2002-07-05 13:30:02 UTC
As issue #23065 is fixed I tested it on Solaris. I works though I
observed deadlock. I filled issue #25371. Marking as WORKSFORME.
Comment 2 Quality Engineering 2003-07-01 15:47:35 UTC
Resolved for 3.4.x or earlier, no new info since then -> verified.

Comment 3 Quality Engineering 2003-07-01 16:44:07 UTC
Resolved for 3.4.x or earlier, no new info since then -> closing.
Comment 4 Jan Chalupa 2003-11-03 14:17:42 UTC
A CLOSED issue mistakenly moved into a NEW state... closing again...
Comment 5 Jan Chalupa 2003-11-03 14:20:07 UTC
... step 2...
Comment 6 Jan Chalupa 2003-11-03 14:23:03 UTC
... step 2...
Comment 7 Jan Chalupa 2003-11-03 14:33:14 UTC
... step 3. CLOSED.