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 24050 - Null Pointer Exception shows up in display area of property sheet
Summary: Null Pointer Exception shows up in display area of property sheet
Status: CLOSED FIXED
Alias: None
Product: db
Classification: Unclassified
Component: Code (show other bugs)
Version: -FFJ-
Hardware: Sun Solaris
: P3 blocker (vote)
Assignee: Radko Najman
URL:
Keywords:
: 25606 (view as bug list)
Depends on: 13345
Blocks:
  Show dependency tree
 
Reported: 2002-05-24 18:59 UTC by Chris Webster
Modified: 2003-06-30 17:17 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Image showing null pointer exception text in display window (41.63 KB, image/jpeg)
2002-05-24 19:00 UTC, Chris Webster 		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 Chris Webster 2002-05-24 18:59:23 UTC 
When displaying the property sheets for the
pointbase connection multiple null pointer
exceptions show up in the display area. see
attached gif
Comment 1 Chris Webster 2002-05-24 19:00:29 UTC 
Created attachment 5958 [details]
Image showing null pointer exception text in display window
Comment 2 Radko Najman 2002-05-27 10:27:56 UTC 
This usually happen if JDBC driver doesn't return all required
DatabaseMetaData.
In the future we should display more describing message.
Comment 3 Jiri Rechtacek 2002-07-10 14:44:54 UTC 
Fix 13345 doesn't help fix this issue. There is a problem with
constructing property. If a property has primitive type Boolean.TYPE
then can return null never. Either declare property's type on
Boolean.class (nb BooleanEditor will be used) or getValue() should
return true/false.
Comment 4 Radko Najman 2002-07-10 15:48:36 UTC 
Fixed (Boolean.TYPE replaced by Boolean.class)
Comment 5 Radko Najman 2002-07-15 14:18:50 UTC 
*** Issue 25606 has been marked as a duplicate of this issue. ***
Comment 6 David Kaspar 2002-11-18 13:32:43 UTC 
Verified in main trunk
Comment 7 Quality Engineering 2003-06-30 17:17:22 UTC 
Resolved for 3.3.x or earlier, no new info since then -> closing.