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.

Bug 14223 - Better handling with invalid beans
Summary: Better handling with invalid beans
Status: CLOSED FIXED
Alias: None
Product: guibuilder
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: All All
: P4 blocker (vote)
Assignee: issues@guibuilder
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-08-07 08:46 UTC by Marian Mirilovic
Modified: 2003-06-30 18:27 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
NullPointerException (1.81 KB, text/plain)
2001-08-07 08:47 UTC, Marian Mirilovic 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Marian Mirilovic 2001-08-07 08:46:28 UTC 
[nb_dev](20010807),[jdk1.3.1](rc1)

Steps to reproduce:
- open/create frame
- move mouse over Form designer

Number of NullPointerException-s arise, it's impossible work with form in this
state - P1.
Comment 1 Marian Mirilovic 2001-08-07 08:47:05 UTC 
Created attachment 2081 [details]
NullPointerException
Comment 2 Marian Mirilovic 2001-08-07 10:13:56 UTC 
Really, the TimerBean is "bad" Bean, this cause firing exception and
would be nice if exception won't be fired.
Comment 3 Tomas Pavek 2001-09-05 15:11:57 UTC 
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...
Comment 4 Tomas Pavek 2001-10-17 17:30:12 UTC 
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.
Comment 5 Tomas Pavek 2001-11-07 12:42:18 UTC 
Another problem is that palette uses NodeListModel which presents all 
nodes always - we cannot exclude "invalid" nodes this way...
Comment 6 Tomas Pavek 2001-11-15 17:10:39 UTC 
Jano, do you think this could be fixed somehow?
Comment 7 Jan Chalupa 2001-11-27 12:38:22 UTC 
Target milestone -> 3.3.1.
Comment 8 Tomas Pavek 2002-04-05 16:49:02 UTC 
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.
Comment 9 Marian Mirilovic 2002-04-12 09:49:59 UTC 
verified in [nb_dev](20020412)
Comment 10 Quality Engineering 2003-06-30 18:27:25 UTC 
Resolved for 3.3.x or earlier, no new info since then -> closing.