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: | Property values should be stored using XMLEncoder/XMLDecoder mechanism | ||
|---|---|---|---|
| Product: | guibuilder | Reporter: | dpociu <dpociu> |
| Component: | Code | Assignee: | issues@guibuilder <issues> |
| Status: | NEW --- | ||
| Severity: | blocker | ||
| Priority: | P2 | ||
| Version: | 5.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | ENHANCEMENT | Exception Reporter: | |
| Attachments: | IDE log | ||
I agree that we should support this type of persistence. Changing to feature request because this is more a lack of a feature than a bug. Created attachment 49891 [details]
IDE log
Attached IDE log by mistake to this bug. Please disregard. (Log belongs to 116952) |
When writing customizers/property editors for visual components currently there is no developer friendly mechanism to persist complext values in the form file other than serialization and using the Netbeans-specific XMLPropertyEditor. In addition, when using XMLPropertyEditor, we also have to "patch" both the development environment and the module's layer.xml file with the following in order to get the form classloader to load the classes for the objects being customized/edited. <!-- form class loader type registration --> <folder name="org-netbeans-modules-form"> <folder name="classloader"> <folder name="system_with_project"> <file name="MySystemAndProjectClasses.txt"> com.mypckage.** </file> </folder> </folder> </folder>