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 14078 - Breakpoints created in Boston aren't deserialized
Summary: Breakpoints created in Boston aren't deserialized
Status: CLOSED WONTFIX
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: -FFJ-
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: Marian Petras
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-07-31 16:29 UTC by L Martinek
Modified: 2001-08-24 08:44 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
exceptions (19.36 KB, text/plain)
2001-07-31 16:30 UTC, L Martinek 		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 L Martinek 2001-07-31 16:29:59 UTC 
[010730_1]

If you create breakpoints in boston and then import settings from this build to pilsen, the breakpoints won't be deserialized in pilsen. It 
causes problems for other teams that depends on debugger (JSP debugging).

If settings from Boston IE are imported the exceptions are thrown during startup (attached).
Comment 1 L Martinek 2001-07-31 16:30:41 UTC 
Created attachment 2020 [details]
exceptions
Comment 2 Marian Petras 2001-08-22 16:28:05 UTC 
This bug is caused by changes in inheritance hierarchy of debugger's
classes. Also distribution of classes within packages has been
changesd since Boston (e.g. AbstractDebugger has been in subpackage
'support', now it is not).
     The only way to fix this bug is to modify NetBeans' object
input stream for loading settings (NbObjectInputStream) or to write a
special method 'readExternal' for reading the old options. This method
would have to be almost precise duplicate of the SystemOption's
'readExternal'. Neither of these is a good solution.
Comment 3 Jan Stola 2001-08-24 08:44:28 UTC 
Wontfix -> Closed.