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 37345 - RuntimeException during Debugger start
Summary: RuntimeException during Debugger start
Status: VERIFIED INVALID
Alias: None
Product: cnd
Classification: Unclassified
Component: Terminalemulator (show other bugs)
Version: 3.x
Hardware: Sun SunOS
: P3 blocker (vote)
Assignee: _ tboudreau
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-11-19 15:20 UTC by Jan Lahoda
Modified: 2008-12-23 08:10 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
The RuntimeException thrown. (1.80 KB, text/plain)
2003-11-19 15:21 UTC, Jan Lahoda
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Lahoda 2003-11-19 15:20:20 UTC
NetBeans build 200311181900, JDK1.4.2.

Each time I try to start the debugger, the
attached RuntimeException occurs. It seems that it
can be a problem in:
org.netbeans.core.output.OutputTabInner
Comment 1 Jan Lahoda 2003-11-19 15:21:26 UTC
Created attachment 12222 [details]
The RuntimeException thrown.
Comment 2 _ tboudreau 2003-11-19 16:15:08 UTC
This is as designed.  It is not actually thrown, just written to the log file to 
encourage users of SplittedPanel to replace it with JSplitPane.  
SplittedPanel will soon be moved to openide.deprecated.  AFAIK 
ErrorManager.INFORMATIONAL warnings will be suppressed in release 
builds.  It's meant to be annoying. 
Comment 3 Jan Lahoda 2003-11-19 16:32:00 UTC
Well, I maybe missed something, but
org.netbeans.core.output.OutputTabInner uses a deprecated class
(org.openide.awt.SplittedPanel). I think this is not OK (regardless
the exception is printed or not) and should be fixed.
Comment 4 _ tboudreau 2003-11-19 17:22:36 UTC
Yes, and I own the output window, and I will fix it there. 
 
If there is no warning, people will continue using SplittedPanel.  This is the 
same type of warning we give for other things (Jesse's recent asynchronous 
action changes, for instance). 
 
Unless I annotated it wrong and you are seeing a stack trace *dialog*, then 
this is working *exactly* the way it is supposed to.  It is not a bug. 
Comment 5 Jan Lahoda 2003-11-19 17:43:06 UTC
Well, I probably did not write it clearly once more. What I was
suggesting by this bug was removing this exception from the log by
*fixing* OutputTabInner, *not* by commenting out the warning in
SplittedPanel (what is the way you understand it).

From my point of view, the exception in the log is a problem, and the
only clean way to remove it is to fix the OutputTabInner so it does
not use the deprecated class. So I supposed you will solve it by using
 JSplitPane instead of SplittedPanel (please note that I never
suggested to remove the warning from the SplittedPanel, in fact I said
I think the problem is in OutputTabInner). I cannot understand what is
the reason why is the issue invalid.

To say it concise: I did not wish you to modify SplittedPanel, but
OutputTabInner.
Comment 6 _ tboudreau 2003-11-19 17:57:26 UTC
Yes, I plan to do that ASAP. 
Comment 7 _ tboudreau 2003-11-19 22:22:55 UTC
FYI, as part of the fix for issue 24824, I have replaced the
SplittedPanel in the output window with a JSplitPane.  So, no more
warnings (at least from the output window).
Comment 8 Marian Mirilovic 2004-03-22 14:43:25 UTC
Honza L. ,
verify your reported issues ASAP after resolution (in the future) ..... ,
 thanks in advance

verified
Comment 9 Quality Engineering 2008-12-23 08:10:10 UTC
moving terminal emulator issues to terminalemulator component.
To see the correct version and target milestone of this issue look at Issue
Activity table.