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.
Summary: | XMLSettingsSupport: Exception not going through error manager | ||
---|---|---|---|
Product: | platform | Reporter: | Torbjorn Norbye <tor> |
Component: | -- Other -- | Assignee: | Jan Pokorsky <jpokorsky> |
Status: | CLOSED INVALID | ||
Severity: | blocker | ||
Priority: | P3 | ||
Version: | 3.x | ||
Hardware: | Sun | ||
OS: | SunOS | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Torbjorn Norbye
2001-10-15 22:05:07 UTC
By the way, I realize what the problem was in my code (I needed to insert a full URL to the .dtd - just like the description said, although I'm puzzled by this - does NetBeans actually go to http://www.netbeans.org/dtds/sessionsettings-1_0.dtd during startup to validate the XML in my .settings file?). The bug that this issue tracks is the fact that the exception was thrown and no error manager appeared showing the exception, or letting me get to the original exception (and there was no justification for the discard-throw-new exception in the code, as also suggested on nbdev.) Reason for using discard-throw-new exception is passing the result to InstnceCookie which cannot throw parser's exceptions. But the origin exception is not lost certainly at least its stacktrace. Calling ErrorManager.annotate(new_ex, old_ex) copies old stacktrace so when you chatch new exception and notify it through ErrorManager both stacktraces are shown. How is user notified it depends on severity and ErrorManager implementation. In regards to looking for DTD. System first search an entity catalog for public id and if none is found out then the url is used. See resources/mf-dtds.xml in core. Resolved for 3.4.x or earlier, no new info since then -> verified Resolved for 3.4.x or earlier, no new info since then -> closing. |