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.
Summary: | Refactor doesn't work with NOT primitive type/ serialized form component property values | ||
---|---|---|---|
Product: | guibuilder | Reporter: | rbelatamas <rbelatamas> |
Component: | Code | Assignee: | issues@guibuilder <issues> |
Status: | NEW --- | ||
Severity: | normal | ||
Priority: | P3 | ||
Version: | 8.1 | ||
Hardware: | PC | ||
OS: | Windows 7 | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | An example |
Description
rbelatamas
2016-05-18 02:16:16 UTC
Interesting problem. It may be possible to deserialize an instance into a different class (i.e. the same class renamed) which then could be serialized back to the GUI form. The problem here is that when the refactoring is running, the GUI builder does not have the new class yet (it is probably not renamed yet, or definitely not compiled). It will be after the refactoring completes. So all GUI refactorings are simplified to deal with this limitation somehow. Here it seems like it can't be overcome. But if there is a trick to read serialized content for a different class (http://stackoverflow.com/questions/2358886/how-can-i-deserialize-the-object-if-it-was-moved-to-another-package-or-renamed), maybe there is also an opposite trick for writing. That would have to be investigated. How can I edit my first comment to insert a break into the long line? :) |