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.
There is a problem with 1. eager initialization of bundles in loaders (because they are used to setDisplayName) 2. the problem that there is no differences between default actions and changed user actions in the serialized bundle. My proposed solution is to create new methods protected String defaultName (); protected SystemAction[] createActions (); that would be called "on demand", when needed, if the user does not change the name or the actions itself. It is also likely good idea to change the serialization protocol, to store "null" as name and list of actions if not modified. Also the deserialization should be enhanced, so it will carefully handle deserialization of old versions (displayname used only if different from default) and actions thrown away...
- Two new methods created to get default display name (actions): protected String defaultDisplayName (); protected SystemAction[] defaultActions (); - Getters getDisplayName (), getActions () modified to return defaults if there are no changes - serialization changed to store only changes (if display name (or actions) doesn't change from default, null will be stored). Integer object representing version will be stored too. - deserialization changed - after reading object (display name or actions) setDisplayName(String) (or setActions(SystemAction[])) will be called only if readed object differs from default.
Fixed. Appropriated bugs were filed against other loaders to use this implementation.
Target milestone -> 3.2
Resolved for 3.4.x or earlier, no new info since then -> closing.