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.
[ BUILD # : 200410311900 ] [ JDK VERSION : J2SE 1.5.0 ] If I associate an extension like "vm" to an object type such as "Textual Objects", this has effect only during the NetBeans session. Nothing is written to my user directory. When I start NetBeans the next time, the association is forgotten.
I'm currently being driven nuts by this. Every time I start Netbeans, I have to add "wsdl" and "wsdd" to the XML object type. Shouldn't this have a high priority? This is a pretty bad regression from previous versions of Netbeans.
True. Verified on custom build of 2004-11-05 sources w/ JDK 1.4.2_04. I can see the modified object types serialized in the loaders.ser file (will attach). Not sure if they're written correctly though. When the IDE tries to deserialize the object types, attempt to read the modified loader settings fails with exceptions (will attach log file fragment). Apparently, the object type's input and output formats are not compatible. I think this should be fixed if possible as it may have other consequences. David, I'm not sure if this is yours. Feel free to re- assign.
Created attachment 18790 [details] loaders.ser including modified object types that cannot be read.
Modified object types serialized in the attached loaders.ser are: Bitmap Objects: added 'bmp' and 'xxx' extensions XML Objects: added 'wsdl' extension
Created attachment 18791 [details] message.log file with exceptions after restart
The fix should be trivial. I'm going to work on it. There exist workaround: when customizing extensions of Object Type you have to "touch" also Actions. For example add separator and immediatelly remove it.
Deserialization simply ignored fact that serialized list of actions may be null. Fixed in: src/org/openide/loaders/DataLoader.java; new revision: 1.6; previous revision: 1.5 Test added: test/unit/src/org/openide/loaders/DataLoaderTest.java; initial revision: 1.1
Created attachment 18794 [details] trunk patch
Yarda, we talked about this. Could you please review the fix. Thanks. Honza, once reviewed by Yarda I will go to reviewers to get the fix to 4.0 unless you tell me otherwise. As I mentioned there is a workaround. On the other hand fix should be really safe.
Yes, please go ahead and follow the integration process for 4.0.
Ok. The problem was simulated and it is clear that after the fix the problem is gone. Go from me.
I was curious when this got broken and found that it is caused by this recent change: User: rkubacki Date: 04/10/13 05:28:14 Modified: loaders/src/org/openide/loaders DataLoader.java Log: no need to check compatibility with boston <http://openide.netbeans.org/source/browse/openide/loaders/src/org/openide/loaders/DataLoader.java.diff?r1=1.4&r2=1.5>
Integrated to release40: src/org/openide/loaders/DataLoader.java; new revision: 1.5.4.1; previous revision: 1.5 test/unit/src/org/openide/loaders/DataLoaderTest.java; new revision: 1.1.2.1; previous revision: 1.1