[jbosstools-issues] [JBoss JIRA] Resolved: (JBDS-343) Project loaded into JBoss DevStudio can't be opened, causes NullPointerException in "EJB3ClasspathContainer.getClasspathEntries()"

[Max Rydahl Andersen (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBDS-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Max Rydahl Andersen resolved JBDS-343.
--------------------------------------

    Fix Version/s: 1.1.0.GA
       Resolution: Duplicate Issue


the problem is that jboss tools assumed the JBoss 4.2 runtime existed (which it won't do in a new workspace)

JBDS 1.1 includes the fixes for this

> Project loaded into JBoss DevStudio can't be opened, causes NullPointerException in "EJB3ClasspathContainer.getClasspathEntries()"
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBDS-343
>                 URL: https://jira.jboss.org/jira/browse/JBDS-343
>             Project: Developer Studio
>          Issue Type: Bug
>    Affects Versions: 1.0.0.GA
>         Environment: Linux Fedora 8, 2.6.24.7-92.fc8
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04)
> Java HotSpot(TM) Client VM (build 1.5.0_12-b04, mixed mode, sharing)
>            Reporter: David Tonhofer
>            Assignee: Max Rydahl Andersen
>             Fix For: 1.1.0.GA
>
>
> A project exported from subversion into JBoss DevStudio cannot be opened. The Eclipse log shows NullPointerException, either at startup or later. Here is the one at startup:
> !ENTRY org.eclipse.core.jobs 4 2 2008-05-23 15:25:55.615
> !MESSAGE An internal error occurred during: "Initializing Java Tooling".
> !STACK 0
> java.lang.NullPointerException
>         at org.jboss.ide.eclipse.as.classpath.core.ejb3.EJB3ClasspathContainer.getClasspathEntries(EJB3ClasspathContainer.java:113)
>         at org.eclipse.jdt.internal.core.JavaModelManager.containerPutIfInitializingWithSameEntries(JavaModelManager.java:547)
>         at org.eclipse.jdt.internal.core.SetContainerOperation.executeOperation(SetContainerOperation.java:49)
>         at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:720)
>         at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1797)
>        ....
> Speculation on what went wrong: The .classpath of the project has a Windows-Nature Absolute Path (a Bad Thing in our mixed environment), somehow created on an Eclipse with manually loaded-in JBoss Tools:
> <?xml version="1.0" encoding="UTF-8"?>
> <classpath>
> 	<classpathentry kind="src" path="src"/>
> 	<classpathentry kind="src" path="test"/>
> 	<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
> 	<classpathentry combineaccessrules="false" kind="src" path="/jb_seam_demox-ejb"/>
> 	<classpathentry kind="lib" path="D:/jboss-seam-2.0.0.GA/lib/testng.jar"/>
> 	<classpathentry kind="con" path="org.jboss.ide.eclipse.as.classpath.core.ejb3.classpathContainer/JBoss 4.2 Server"/>
> 	<classpathentry kind="output" path="bin"/>
> </classpath>

-- 
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