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: | IllegalStateException: [Winsys] TopComponent org.netbeans.modules.xml.text.TextEditorComponent throws runtime exception from its componentActivated() method. Please repair it! Probable cause is at org | ||
---|---|---|---|
Product: | xml | Reporter: | hdhero <hdhero> |
Component: | Text-Edit | Assignee: | Samaresh Panda <samaresh> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | CC: | isai, jinath, teras |
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://statistics.netbeans.org/exceptions/detail.do?id=42702 | ||
Issue Type: | DEFECT | Exception Reporter: | 42702 |
Attachments: | stacktrace |
Description
hdhero
2008-04-23 08:49:00 UTC
Created attachment 60591 [details]
stacktrace
java.lang.IllegalStateException: [Winsys] TopComponent org.netbeans.modules.xml.text.TextEditorComponent throws runtime exception from its componentActivated() method. Please repair it! Probable cause is at org.netbeans.modules.xml.text.TextEditorComponent.componentActivated(TextEditorComponent.java:167) This issue has already 20 duplicates Reopening - reproduced in NetBeans IDE 6.1 (Build 200805300101) stenlee, this issue has been fixed in subsequent release *after* NetBeans 6.1 was released. You can certainly reproduce it in NetBeans 6.1 even with the latest patch installed, but it's not a reason to reopen this issue if there's no plan to port the fix into NetBeans 6.1 fixes codeline. If you insist on fixing this issue for NetBeans 6.1 you have got basically two options: #1 consider buying commercial support and request this issue to be fixed for NetBeans 6.1. More information about commercial support can be found at http://www.netbeans.org/kb/support.html #2 the CDDL + GPL v2 dual licensing allows you to fork the "development" and fix it yourself in your private repository and build. It's opensource, no one will do any obstacles if you choose this way, but take into account that maintenance of private repository and build could eventually (in long term project) be a bit more expensive than buying commercial support (calculations have to be done case by case) Returning back to RESOLVED-FIXED state. |