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 15581 - Deserialized editor topcomponents don't save data on disk
Summary: Deserialized editor topcomponents don't save data on disk
Status: CLOSED WORKSFORME
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 3.x
Hardware: PC Linux
: P4 blocker (vote)
Assignee: Jiri Rechtacek
URL:
Keywords:
: 15578 (view as bug list)
Depends on:
Blocks:
 
Reported: 2001-09-18 09:57 UTC by Peter Zavadsky
Modified: 2008-12-23 09:32 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
exeptions in console during start (6.96 KB, text/plain)
2001-09-18 09:58 UTC, Peter Zavadsky
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Zavadsky 2001-09-18 09:57:02 UTC
Orion (build 010912)
Note: Project module disabled, also other ones (but I think those are not
important for this case).

1) Working on java sources, opened in editing ws, some of them [read-only].
2) Restarted IDE
3) Exceptions in console - see attachment
4) Working on deserialized topcomponents (of course not on the read-only's)
seemed to be fine, but it has one big cave, the changes weren't propagated to
the disk, it seemed just to work on document with no file connection
-> data loss.
Comment 1 Peter Zavadsky 2001-09-18 09:58:20 UTC
Created attachment 2578 [details]
exeptions in console during start
Comment 2 Jan Zajicek 2001-09-18 11:00:00 UTC
*** Issue 15578 has been marked as a duplicate of this issue. ***
Comment 3 Jiri Rechtacek 2001-11-01 15:07:30 UTC
[build Nov 01]
I'm not able to see any exceptions if I follow the described steps.
Please reopen this issue if it appeared again. Thanks.
Comment 4 Jiri Rechtacek 2001-11-01 15:32:57 UTC
I apologized I edited another issue if I wanted.
Comment 5 Jiri Rechtacek 2001-11-01 15:47:36 UTC
Observation: This issue appeared only if Projects module is disable.
Calling fo = getComponentsFolder(FOR_READING).getFileObject(stringId,
"ser") returns null.
Comment 6 Jan Chalupa 2001-11-27 11:51:38 UTC
Target milestone -> 3.3.1.
Comment 7 Jan Chalupa 2001-11-27 11:55:02 UTC
Target milestone -> 3.3.1.
Comment 8 _ ttran 2001-11-29 17:24:23 UTC
happens only when projects module is disabled, not usual situation => P4
Comment 9 David Simonek 2002-01-09 10:24:11 UTC
Jiri, can you take this one again? You did some observations in the
past so you have good startup position :-)
Peter, please assist Jiri with reproduction etc. Thanks.
Comment 10 Jiri Rechtacek 2002-01-10 10:31:31 UTC
[Jan 09 release33]
I'm not able to see any exceptions if I follow the described steps.
The changes on edited files are stored correctly too.
Because, I saw in Nov01 build I didn't see it with today's build, it
was fixed already. Please reopen this issue if it appeared again. Thanks.
Comment 11 Quality Engineering 2003-07-01 16:06:28 UTC
Resolved for 3.4.x or earlier, no new info since then -> verified.

Comment 12 Quality Engineering 2003-07-01 16:50:59 UTC
Resolved for 3.4.x or earlier, no new info since then -> closing.