[ https://jira.jboss.org/jira/browse/JBIDE-5980?page=com.atlassian.jira.plu... ] Vitali Yemialyanchyk updated JBIDE-5980: ---------------------------------------- Summary: Constantly get NPE when open JBDS workspace in Eclipse with WTP (+others) and then open it back in JBDS (was: Constantly get NPE when open JBDS in Eclipse with WTP (+others) and then open it back in JBDS) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-5980?page=com.atlassian.jira.plu... ] Denis Golovin updated JBIDE-5980: --------------------------------- Component/s: UpStream -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-5980?page=com.atlassian.jira.plu... ] Tom Bryan commented on JBIDE-5980: ---------------------------------- I'm also seeing this issue: Windows Vista Eclipse 3.5.2, build 20100218-1602 JBoss Tools 3.1 JDK 1.6.0_19 Sometimes, when I start Eclipse, I get a NPE, such as the one listed above (an example from my workspace pasted below, but I think that they are the same). Once I get this error, I basically have to restart. Otherwise, I start seeing lots of strange problems, such as compilation errors and other errors reported by JDT in the error log. If I successfully start Eclipse without getting this error, then the same project builds just fine, and I don't see the other JDT errors. This problem leaves our developers completely unable to work. They have to keep restarting Eclipse until they can get a restart without an error. If anyone has a fix or even a workaround, I'd love to hear it. The problem is intermittent, so perhaps it is some sort of race condition. Interestingly, I haven't seen the problem yet when running the same tools under Linux (same machine booted to a different OS). java.lang.NullPointerException at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:280) at org.eclipse.emf.common.notify.impl.NotifyingListImpl.dispatchNotification(NotifyingListImpl.java:267) at org.eclipse.jem.internal.util.emf.workbench.ProjectResourceSetImpl$SynchronizedResourcesEList.dispatchNotification(ProjectResourceSetImpl.java:335) at org.eclipse.emf.common.notify.impl.NotifyingListImpl.addUnique(NotifyingListImpl.java:300) at org.eclipse.emf.common.util.AbstractEList.add(AbstractEList.java:307) at org.eclipse.jem.internal.util.emf.workbench.ProjectResourceSetImpl$SynchronizedResourcesEList.add(ProjectResourceSetImpl.java:81) at org.eclipse.jem.internal.util.emf.workbench.ProjectResourceSetImpl.createResource(ProjectResourceSetImpl.java:392) at org.eclipse.wst.common.internal.emfworkbench.integration.ProjectResourceSetEditImpl.createResource(ProjectResourceSetEditImpl.java:48) at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandCreateResource(ResourceSetImpl.java:239) at org.eclipse.jem.internal.util.emf.workbench.ProjectResourceSetImpl.getResource(ProjectResourceSetImpl.java:693) at org.eclipse.jst.jee.model.internal.JEE5ModelProvider.getModelResource(JEE5ModelProvider.java:155) at org.eclipse.jst.jee.model.internal.EAR5ModelProvider.getModelObject(EAR5ModelProvider.java:50) at org.eclipse.jst.j2ee.project.EarUtilities.getEARLibDir(EarUtilities.java:372) at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.getBaseEARLibRefs(J2EEComponentClasspathContainer.java:321) at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.update(J2EEComponentClasspathContainer.java:211) at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.install(J2EEComponentClasspathContainer.java:351) at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathInitializer.initialize(J2EEComponentClasspathInitializer.java:47) at org.eclipse.jdt.internal.core.JavaModelManager.initializeContainer(JavaModelManager.java:2642) at org.eclipse.jdt.internal.core.JavaModelManager$11.run(JavaModelManager.java:2548) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800) at org.eclipse.jdt.internal.core.JavaModelManager.initializeAllContainers(JavaModelManager.java:2588) at org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:1808) at org.eclipse.jdt.core.JavaCore.initializeAfterLoad(JavaCore.java:3410) at org.eclipse.jdt.internal.ui.InitializeAfterLoadJob$RealJob.run(InitializeAfterLoadJob.java:35) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira