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.
I recently downloaded netbeans 3.3 beta 4 and after installing I encountered a problem when trying to run the program. After entering the default directory for the projects, etc. it appeared the the application froze. To check to see if a error was happening I went to the dos prompt and ran runide and received the following error. It appears to me that it's a simple case of a class not being added to the installation package. I am going to try downloading just the zip. Hope this helps you out. javax.xml.parsers.FactoryConfigurationError: java.lang.ClassNotFoundException: org.netbeans.core.xml.NbSAXParserFactoryImpl at javax.xml.parsers.SAXParserFactory.newInstance (SAXParserFactory.java:120) at org.openide.xml.XMLUtil.createXMLReader(XMLUtil.java:69) at org.openide.xml.XMLUtil.createXMLReader(XMLUtil.java:43) at org.openide.loaders.XMLDataObject.<clinit>(XMLDataObject.java:935) at org.netbeans.core.NbTheme.parseTheme(NbTheme.java:110) at org.netbeans.core.NbTheme.<init>(NbTheme.java:90) at org.netbeans.core.Main.run(Main.java:118) at org.openide.TopManager.initializeTopManager(TopManager.java:120) at org.openide.TopManager.getDefault(TopManager.java:81) at org.netbeans.core.Main.main(Main.java:325) at org.netbeans.core.TopThreadGroup.run(TopThreadGroup.java:90) at java.lang.Thread.run(Thread.java:484)
we've heard of a similar case: you probably have some jar files under <jdk>\jre\lib\ext which conflicts with the versions of the same jar files bundled with NB. Please check Next time when you report bugs, please always provide information about your versions of JDK and OS. Thanks
To Chadwick M. Baatz: is my evaluation correct? The same thing happened to other users. I cannot reproduce the bug here. Also lowering prio to P2, not a showstopper for the release, IMHO
Comment from Chadwick : It appears that this has taken care of the issue. I apologize for the lack of information earlier, I am running Win 2000 Professional, with JDK 1.3. I trust that you will resolve this conflict in the future. I believe it happened because I had already installed the XML parser classes from w3c. Thank you, Chadwick M. Baatz
that's it. We cannot override jar files installed in <jdk>/jre/lib/ext. If the users put the "wrong" jars there, then there will be troubles.
I believe that you should look for these XML files and if there use them instead. I know that the install shield can verify if they exists for you and at least you should identify exactly what JAR files are causing the issue and if they exists prompt the user to let them know that there will be an issue. I believe that this is critical, since if you run the IDE as normal in the windows environment you will get no error message, it just appears that the IDE hangs. This can be confusing to some users who are not aware of how to run the IDE from console. I think that you should revisit this idea and create a work around, because of the fact a lot of people have been using XML. It would be ignorant to put a product into the market without addressing this issue. It is poor practice to place any type of product into the market place when there is a verified bug, and at a minimum fix or work around. At least I employer you to create an alert during the install to notify users who are going to have this problem. A failure to do so will only leave users confused and not willing to use your product.
Agreed that this can be a type of hard to detect trouble for the users. But your suggested measures don't work. The users can always add jar files into <jdk>/jre/lib/ext *after* the IDE is installed and suddenly things stop working. I can only think of - short-term: put an alert into README, FAQ - long-term: ignore the jars in <jdk>/jre/lib/ext completely. This is not trivial to implement. We have to override the default java app classloader. This of course actually invalidates the whole Java Extension Framework idea. However based on our experience that idea does not work in practice and causes more troubles than it's worth (c.f. this bug)
> - long-term: ignore the jars in <jdk>/jre/lib/ext completely. second thought: we actually cannot always afford this solution. The user may installs some software (like accessibility aid) which would work for all java software into this place. If we ignore its jars then that software stops working. A radical assessment would be to blame the one who places the "XML parser classes from w3c" under jre/lib/ext (either the installer or the user). We can ensure the IDE with work with a certain OS/JDK configurations but nobody can make sure that it will work with OS/JDK plus an arbitratrary set of java extensions. I am closing this bug as WONTFIX and will add a note to the README file.
Just note that this issue is in nb from 3.2 and was mentioned in the readme for this release. There are several similar issues in IZ that are closed as wontfix or invalid with recommendation to remove i.e xerces.jar from the {jdk_home}/jre/lib/ext/ folder. You have to remove the jar, only renaming sometimes do not help.
x
*** This issue has been marked as a duplicate of 17358 ***
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.