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 63238 - CNFE when is selectet action node in xml layer
Summary: CNFE when is selectet action node in xml layer
Status: VERIFIED FIXED
Alias: None
Product: apisupport
Classification: Unclassified
Component: Project (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: Jesse Glick
URL:
Keywords:
: 62514 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-08-29 13:06 UTC by pzajac
Modified: 2006-02-14 17:55 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
exception (3.68 KB, text/plain)
2005-08-29 13:07 UTC, pzajac
Details

Note You need to log in before you can comment on or make changes to this bug.
Description pzajac 2005-08-29 13:06:14 UTC
[200508281800]
Steps to reproduction:
1) Create a TopComponent from wizard. A action is created and inserterd into
layer.xml 
2) select the new action in layer.xml node. ClassNotFoundException is thrown. 
BTW it is quite risky to load created class is running ide.
Comment 1 pzajac 2005-08-29 13:07:05 UTC
Created attachment 24304 [details]
exception
Comment 2 Jesse Glick 2005-08-29 18:17:45 UTC
Weird. I thought I fixed this in NbErrorManager.java several days ago:

----------------------------
revision 1.58
date: 2005/08/25 02:34:06;  author: jglick;  state: Exp;  lines: +24 -36
Removing lastException hack. Maybe it is useful sometimes, but I have observed
it to force printing of unwanted
stack traces from exceptions (CNFE from InstanceSupport) which get some
annotation but are later caught and
(supposed to be) ignored.
----------------------------

When I try it on my normal dev user dir, I get the exception. But when I try the
same thing on a fresh dev build in a fresh user dir, I do not.

Can you supply more precise steps to verify, making sure you are using a fresh
dev build and fresh user dir and new projects? If I could reproduce I could fix it.
Comment 3 Jesse Glick 2005-08-30 00:03:34 UTC
Ah, I think I found the trick: the project must be cleaned (not compiled), or it
will not happen. So maybe the patch to NbErrorManager was unnecessary.
Comment 4 Jesse Glick 2005-08-30 00:14:18 UTC
Found it. InstanceSupport.findHelp was the culprit.
Comment 5 Martin Krauskopf 2005-08-30 00:25:34 UTC
Probably the issue 62514 is the same problem. It would be nice from you if you
would kill two birds with one stone :)
Comment 6 Jesse Glick 2005-08-30 02:12:43 UTC
*** Issue 62514 has been marked as a duplicate of this issue. ***
Comment 7 Jesse Glick 2005-08-30 06:35:37 UTC
committed   * Up-To-Date  1.13       
openide/loaders/src/org/openide/loaders/InstanceSupport.java
committed   * Up-To-Date  1.2         openide/util/src/org/openide/util/HelpCtx.java
Comment 8 pzajac 2005-09-01 16:01:32 UTC
v