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 23447 - [ustudy] Closing a project doesn't close the source files.
Summary: [ustudy] Closing a project doesn't close the source files.
Status: CLOSED FIXED
Alias: None
Product: projects
Classification: Unclassified
Component: Generic Infrastructure (show other bugs)
Version: 3.x
Hardware: PC All
: P3 blocker (vote)
Assignee: Pavel Buzek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-05-14 09:39 UTC by Vitezslav Stejskal
Modified: 2003-07-01 14:17 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 Vitezslav Stejskal 2002-05-14 09:39:57 UTC 
Implement way in which project could tell components that it is being closed. Java sources 
component then use this notification to close all edited files belonging to it.
Comment 1 Pavel Buzek 2002-05-17 13:32:24 UTC 
When the project is being removed from Workplace, it asks all its data objects for close cookie and 
closes them. This may show as a performance problem in future, but is IMO good enough for now.

The other alternatives considered were:
1. Get the list of open data objects from the editor. The disadvantage would be that objects open in a 
different way (not in the Editor component) would not be closed.
2. Listen for creation of data objects on DataLoaderPool. Cache all DO created while the prj is open and 
then close these. The disadvantage is that some DO may survive close and reopen of project and thus they 
are not recreated (and they do not get in that cache).
Comment 2 Milan Kubec 2002-08-08 10:51:34 UTC 
Verified.
Comment 3 Quality Engineering 2003-07-01 14:17:18 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.