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.
A lot of developers is not satisfied with the way how InstanceDataObject .settings files store their objects into file. Plain serialization is not enough, there is a need for custom format, but still the support of IDO.instanceOf (...) and module enabled/disabled state are valuable and thus working with plain XML data objects via Environment.Provider is not as confortable as plugin convertor into IDO. The convertor should be able to encode/decode an object to XML format of .settings file and to provide a filter to inform the IDO when the object is changed and when it needs to be saved (currently done by PropertyChangeListener). Goal of this task is to design API for convertors and find a way how they will be registered and found so IDO can easily use them.
Also support for JDK1.4 archiver should be enabled.
Right now it is possible to build the formater on features implemented as part of issue 17934: Formater f = (Formater)new InitialContext ().lookup ("xml/formaters/org/openide/windows/TopComponent")
I would like to add that it should by default be avoided that in the code editor on every vertical cursor movement a disk I/O is initiated. This currently happens in version 3.3. Quoting Petr Nejedly <petr.nejedly@sun.com> from his post in netbeans.nbusers on Tue, 08 Jan 2002 12:37:05 +0100: "As I wrote before, we should have the ability for a SessionSetting to express its own policy of saving its state. Objects that change their state frequently don't like automatic save."
*** Issue 17983 has been marked as a duplicate of this issue. ***
Do not forget about our archiver reader implementation at http://openide.netbeans.org/issues/showattachment.cgi?attach_id=1575
Removed the dependence on #19903 issue (JNDI). The task was posponed to 4.0 by the core team. The code handling the old serialdata format was separated from the openide to the core to ensure backward compatibility. The custom format is handled via the Settings API provided by the core/settings module. For more details see API docs (ant javadoc). Examples of usage are available in the core/settings/examples module or as unit tests. The archiver format integration was postponed for the meantime.