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: | Better handling with invalid beans | ||
---|---|---|---|
Product: | guibuilder | Reporter: | Marian Mirilovic <mmirilovic> |
Component: | Code | Assignee: | issues@guibuilder <issues> |
Status: | CLOSED FIXED | ||
Severity: | blocker | CC: | jrojcek |
Priority: | P4 | ||
Version: | 3.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | NullPointerException |
Description
Marian Mirilovic
2001-08-07 08:46:28 UTC
Created attachment 2081 [details]
NullPointerException
Really, the TimerBean is "bad" Bean, this cause firing exception and would be nice if exception won't be fired. There should be better and more robust handling with invalid beans: - if the bean class cannot be loaded, the corresponding palette item probably should not be displayed at all (but should be seen in options, maybe also with some notification), - if the class is present, but a default instance cannot be created, there should be an error message with anotated exception. No uncaught exceptions should be thrown around... The second part (problems with adding invalid beans to form) has been already fixed. The problem with invalid palette items remains - seems to be mainly issue of instance support in openide. It also blocks issue 15109. Another problem is that palette uses NodeListModel which presents all nodes always - we cannot exclude "invalid" nodes this way... Jano, do you think this could be fixed somehow? Target milestone -> 3.3.1. I've just done some changes to Component Palette - it does not use NodeListModel anymore, being able to hide invalid items. So I think this issue can be finally considered as fixed. verified in [nb_dev](20020412) Resolved for 3.3.x or earlier, no new info since then -> closing. |