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.
Created attachment 108348 [details] Test and impl for automatic reload if underlaying store file is changed During GeeCON 2011 Hackergarten me and Jakub Milkiewicz worked on a test and an improvement to NbPreferences, to be able to reload when its underlaying storage file changes. I guess we succeeded to improve current state. I'll attach Jakub's patch that includes test and an implementation to make the test pass. Yulia, can you review the code and if you are OK with the implementation apply it? I believe this change would help you improve state of bug 197594 too.
Integrated into 'main-golden' Changeset: http://hg.netbeans.org/main-golden/rev/abdf3b52a520 User: Yulia Novozhilova <ynov@netbeans.org> Log: Fix #198665 - NbPreferences don't reload when underlying file is changed
Thanks to Jarda and Jakub for the patch!
Your welcome. It was a pleasure to develop with Jaroslav. I hope we can organize some hacking at least next year.
I think this change has problems, see bug 197594 comment 21
Integrated into 'releases' Changeset: http://hg.netbeans.org/releases/rev/1cdc8b3c5503 User: Yulia Novozhilova <ynov@netbeans.org> Log: Fix #198665 NbPreferences don't reload when underlying file is changed
> I think this change has problems, see bug 197594 comment 21 Yes, we know this is not full solution to bug 197594 (especially the delivery of events is missing). Jakub and me had just one morning to implement this. Thus I reported this new bug rather modifying the old one.
(In reply to comment #6) > ... this is not full solution to bug 197594 ... I was thinking more of the performance and synchronization issues introduced by a file modification rather than a file replace approach.
The discussion in bug 197594 indicated that this fix should *not* be in 701. It was added 701 on 2011-06-14 as indicated in comment 5. Was it taken out?
Yes: http://hg.netbeans.org/releases/rev/4d80866be327
This should be now fixed. See comment 40 in #197594