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.
This bug was originally marked as duplicate of bug 210236, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related. Build: NetBeans IDE 7.2 (Build 201207171143) VM: Java HotSpot(TM) Client VM, 14.3-b01, Java(TM) SE Runtime Environment, 1.6.0_17-b04 OS: Windows 7 User Comments: lallafa: just started a fresh installation of 201204210400 Stacktrace: java.lang.IllegalArgumentException: No parser for mime type: text/x-java at org.netbeans.modules.parsing.api.ParserManager.findParser(ParserManager.java:394) at org.netbeans.modules.parsing.api.ParserManager.parseWhenScanFinished(ParserManager.java:353) at org.netbeans.api.java.source.JavaSource.runWhenScanFinished(JavaSource.java:578) at org.netbeans.modules.j2ee.metadata.model.api.support.annotation.AnnotationModelHelper.runJavaSourceTaskWhenScanFinished(AnnotationModelHelper.java:218) at org.netbeans.modules.j2ee.dd.impl.webservices.annotation.WebservicesMetadataModelImpl.runReadActionWhenReady(WebservicesMetadataModelImpl.java:105) at org.netbeans.modules.j2ee.metadata.model.api.MetadataModel.runReadActionWhenReady(MetadataModel.java:185)
Created attachment 124384 [details] stacktrace
I have no idea why there is no mime type for "text/x-java". This is out of webservices area. I'm not sure about correctness of Product/Component. Please reassign the issue in case it they are wrong.
*** Bug 221109 has been marked as a duplicate of this bug. ***
I have duplicated all reports before bug #210236 was fixed to that bug. I filled: http://statistics.netbeans.org/exceptions/detail.do?id=194953 for one report from 7.2 I have no explanation for. Now, to the remaining reports: 627011, 625513, 625406, 623583 and 605080. Looking at their messages.log, all these reports have one in common: the code from java.source.JavaSource is run, but the java.source module is not listed in the "Turning on modules:" section. So it seems that the module system is running code from a module that is not enabled! I don't think that should be happening -> module system.
Created attachment 127886 [details] stacktrace
FYI: Jirka mentioned today that he knows how to simulate a case where some modules are running, but not printed in the messages.log
Any new signs this is still a problem?