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 14397

Summary: InstanceDataObject.create can save an object twice
Product: platform Reporter: Jaroslav Tulach <jtulach>
Component: -- Other --Assignee: rmatous <rmatous>
Status: CLOSED FIXED    
Severity: blocker CC: jpokorsky, pzajac
Priority: P2 Keywords: PERFORMANCE
Version: 3.x   
Hardware: PC   
OS: Linux   
Issue Type: DEFECT Exception Reporter:
Bug Depends on:    
Bug Blocks: 14331    
Attachments: Stacktrace that shows that the first filesystem is "resaved" once again
stack trace

Description Jaroslav Tulach 2001-08-14 08:49:29 UTC 
I have added a stack trace to core.ExLocalFileSystem.writeObject to see home
many times it is saved.

Then I created one filesystem and everything was ok (FileSystems/Mount) but when
I tried to create second one a filesystem has been serialized twice.
Comment 1 Jaroslav Tulach 2001-08-14 08:52:37 UTC 
Created attachment 2154 [details]
Stacktrace that shows that the first filesystem is "resaved" once again
Comment 2 Jaroslav Tulach 2001-08-14 08:53:37 UTC 
Without fixing this the q-build stoper #14331 will never be fixed.
Comment 3 Jan Pokorsky 2001-08-14 18:05:28 UTC 
fixed
Comment 4 pzajac 2002-09-10 17:09:41 UTC 
Jane, could you explain me your fix? I added stacktrace dump to
AbstraFilesystem. And I saw two writeObject of mounted local filesystem.
Comment 5 pzajac 2002-09-10 17:14:49 UTC 
Created attachment 7365 [details]
stack trace
Comment 6 Jan Pokorsky 2002-09-10 17:25:29 UTC 
It is caused by attaching an instance to a settings convertor by the 
new settings framework if created via IDO.create. Is that hurting 
anything?
Comment 7 rmatous 2002-09-23 11:18:22 UTC 
setInstance invokes storing useless - then setInstance doesn`t call
runAndWait any more.
Comment 8 David Simonek 2003-01-15 12:02:46 UTC 
Guys, I'm returning version field to 3.3 dev and target milestone to
3.3, as this bug was fixed 2001-08-14.
Comment 9 pzajac 2003-02-12 17:04:35 UTC 
works correctly in 200202120100
Comment 10 Quality Engineering 2003-07-01 16:32:39 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.