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 46775 - DelegatingNodeActionsProvider cannot handle UnknownTypeException
Summary: DelegatingNodeActionsProvider cannot handle UnknownTypeException
Status: CLOSED INVALID
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 4.x
Hardware: Sun SunOS
: P2 blocker (vote)
Assignee: issues@debugger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-07-30 02:57 UTC by ivan
Modified: 2010-04-29 09:18 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
stack trace (2.35 KB, text/plain)
2004-07-30 02:59 UTC, ivan 		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 ivan 2004-07-30 02:57:54 UTC 
I've provided my own breakpoint nodes and when I 
use the context menu I get the attached exception.
(Note that this is with the jpda module turned off,
which is different from earlier emails examples).
Comment 1 ivan 2004-07-30 02:59:00 UTC 
Created attachment 16570 [details]
stack trace
Comment 2 Jan Jancura 2004-08-02 10:19:16 UTC 
Looks like you do not have NodeActionsProvider registerred for your
node type.

If you create a new node type (FunctionBreakpoint) you should register
all type of models for it:
TreeModel, NodeModel, NodeActionsProvider, TableModel
Comment 3 ivan 2004-08-03 00:48:21 UTC 
Correct, I had mis-registered my NodeActionsProvider.
But I"m confused. Each model query is supposed to throw
a UTE on objects it doesn't recognize. This shouldn't show up
as user-visible exceptions, it should silently fail. No so?

Also, you ~ said "new node type requires models". Did you
really mean that?
I typically associate the model set with views not with node types.
Then each model query switches on the node type.
Comment 4 Quality Engineering 2010-04-29 09:18:33 UTC 
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.