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.
Editor window can be lost and exception is thrown when working with saved project and original project. Another issue is that first saved project doesn't contain all windows openned in original project. Steps to reproduce: 1) open fresh clean IDE 2) open java source file in Default Project 3) open Project Manager and save Default project by action Save as, e.g. Default-copy1 4) switch to project Default-copy1 and editor is missing there = bug 1 5) open Project Manager and save another Default project by action Save as, e.g. Default-copy2 6) switch to project Default-copy2, editor should be there 7) switch to project Default and close editor with java file 8) switch to project Default-copy2 and editor is missing and exception is thrown
Created attachment 3787 [details] exception stack trace
Problem is that there is no support for active project to be saved when Save As action is invoked. (Save As itself just copies project folder). Project folder of active project on disk does not contain current project status - current status is only in memory. Reassigning to projects.
Serious enough to be P2.
Serious, but almost unsolvable for 3.3.x. Ugly solution is to disable 'Save As' for opened project, nicer solution is to save winsys before the action is performed and finally correct solution is to rewrite winsys to keep its persistant state up-to-date with in-memory changes. In fact, this problem doesn't involve window system only, but all the project stuff including settings, filesystems, etc. Window system is the worst case because it doesn't persist its state when change occures, but on project close event only. Generaly there isn't any way in the architecture how to ensure that all the project stuff gets saved on request. In other words everything in the project (including window system) is responsible to keep its persistant state synchronized with in-memory state. Since this change isn't realistic for 3.3.x I would implement saving of winsys prior the 'Save As' action.
Project module forces winsys saving whenever the project needs to be saved. This dependency between projects and core will be removed after the winsys will persist its state automaticaly on each change. Dafe, please, let me know ... Fixed in release33.
Verified in release33-200201170331.
Resolved for 3.4.x or earlier, no new info since then -> closing.