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.
Forte for Java, EE v. 3.0 (Build 20020205-1842) - select a folder - push F1 - IDE is going down - some XML description file in some module of context sensitive help is corupted - you are not able to recognize in which module is problem - IDE should not crash
Please correct your xml file asap. Also please attach the corrupted xml file to this issue, so we can create some regression tests when this gets fixed. Thanks. IDE shouldn't crash, so leaving this at openide. Lower priority to P2. Jesse can we avoid this or is this JavaHelp bug?
the bad XML description file is in web/advanced module. the responsible person will be contacted
*** Issue 20236 has been marked as a duplicate of this issue. ***
What do you mean "IDE goes down"?? HotSpot crash? Stack trace? What? Certainly if your JavaHelp is invalid, an exception will be thrown. I don't think I have ever seen the IDE "crash" however, it just prints a nasty message and does not open help. Please reopen when you have details attached - files to reproduce, ide.log, etc.
OK, now I see a log file in #20236, but still waiting for steps to reproduce. Note that all but the last exception in that log file indicate that it has been caught by the error manager. The last one does not, however according to sources any Throwable thrown from that line in JavaHelp.java gets caught and reported and the error should be recovered from.
win 2000; jdk 131; Forte for Java, EE v. 3.0 (Build 20020207-0704) - start runide.exe (IDE and command line windows are opened) - select a folder - push F1 - both windows are closed IDE should react better, when context sensitive help files are corrupted logfile is attached
Created attachment 4599 [details] ide log
Is the problem reproducible on all platforms? AFAIK no Java code other than System.exit() is supposed to cause the IDE to exit immediately, and the JavaHelp integration certainly does not call System.exit(). Sounds like a low-level VM error to me, perhaps. Reproducible with different JDKs too, e.g. 1.3.1_02 or 1.4rc? (I run Linux so I want to know if I will be able to reproduce on my own machine.)
Also I was unaware of the existence of such a build and have no idea where to find it. pilsen branch you are talking about? Is there a SWAN download URL or NFS mount location where I could get it?
I am sorry, but I do not have enough time resources for better testing. You can download the build from this: http://ffjbuilder.czech.sun.com:8080/BuildResults?days=1&version=orion
Ah, Orion, I was looking at Pilsen builds. Thanks, I am downloading this and will try it.
I have updated the JavaHelpSearch engine version in the jsp.hs file. I think this was the problem. I will check the continuous build to make sure the fix was correct.
*** Issue 20281 has been marked as a duplicate of this issue. ***
Reproducible on Linux, JDK 1.4 too. Found serious bug in JavaHelp 1.1.2_02, cannot work around. BugTraq: #4635290
This will be fixed in the next release of JavaHelp. In the meantime the problem is an incorrectly specified search engine in the users helpset file. Correct that and it will work.
*** Issue 20698 has been marked as a duplicate of this issue. ***
Workaround might be possible, will see.
See issue #20751 for proposed workaround.
*** Issue 28709 has been marked as a duplicate of this issue. ***