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 14024 - InstanceNode initName is poorly written
Summary: InstanceNode initName is poorly written
Status: CLOSED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Data Systems (show other bugs)
Version: 3.x
Hardware: Sun SunOS
: P2 blocker (vote)
Assignee: Jan Pokorsky
URL:
Keywords:
: 14643 (view as bug list)
Depends on:
Blocks: 13815
  Show dependency tree
 
Reported: 2001-07-27 15:32 UTC by anovak
Modified: 2008-12-22 15:42 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 anovak 2001-07-27 15:32:51 UTC 
In this method, somebody invokes "bean = i().instanceCreate();" which is
unacceptable. It creates beans just for getting their names. If such a bean
creates a thread in its constructor ...
Comment 1 Tomas Pavek 2001-09-05 16:46:48 UTC 
Moreover, this raises another problem with InstanceSupport. If 
instance creation fails on InstantiationException (e.g. the class has 
not public empty ctor), the exception is "converted" to 
ClassNotFoundException. InstanceSupport remebers this exception and 
next time when asked for class (by instanceClass() method) it 
automatically throws it - although the class is valid...
I think this should be fixed too.
Comment 2 Jan Pokorsky 2001-09-05 17:05:04 UTC 
I have prepared a fix for InstanceNode and will check it in 
trunk today.

Tomasi if you are convinced about bug in InstanceSupport why don't you 
fill new bug in Issuezilla? BTW how can be bean class valid without 
empty constructor? I did not see code in InstanceSupport but it is 
strange to use InstanceDataObject if you assume your class is not 
valid, is it?
Comment 3 Jan Pokorsky 2001-09-05 19:23:28 UTC 
fixed in InstanceNode.java, v1.11
Comment 4 Jan Pokorsky 2001-09-05 19:32:46 UTC 
*** Issue 14643 has been marked as a duplicate of this issue. ***
Comment 5 Quality Engineering 2003-07-01 16:05:45 UTC 
Resolved for 3.4.x or earlier, no new info since then -> verified
Comment 6 Quality Engineering 2003-07-01 16:39:49 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.