Error after updating to gpd 3.0.6

[forjbpm]

Hi,
I updated my eclipse plugin to jbpm-gpd-3.0.6 from 3.0.5. Now I get following error whenever I click on any existing project:

Unhandled event loop exception
Reason:
java.lang.NullPointerException
Exception in thread "Text Viewer Hover Presenter" java.lang.NullPointerException
at org.jbpm.ui.util.JbpmClasspathContainer.getJarNames(Unknown Source)
at org.jbpm.ui.util.JbpmClasspathContainer.createJbpmLibraryEntries(Unknown Source)
at org.jbpm.ui.util.JbpmClasspathContainer.getClasspathEntries(Unknown Source)
at org.eclipse.jdt.internal.core.JavaModelManager.containerPutIfInitializingWithSameEntries(JavaModelManager.java:297)
at org.eclipse.jdt.core.JavaCore.setClasspathContainer(JavaCore.java:3855)
at org.jbpm.ui.util.JbpmClasspathContainerInitializer.initialize(Unknown Source)
at org.eclipse.jdt.internal.core.JavaModelManager.initializeContainer(JavaModelManager.java:1591)
at org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:1040)
at org.eclipse.jdt.core.JavaCore.getClasspathContainer(JavaCore.java:1326)
at org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath(JavaProject.java:2039)
at org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath(JavaProject.java:1947)
at org.eclipse.jdt.internal.core.JavaProject.buildStructure(JavaProject.java:332)
at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:233)
at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:488)
at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:232)
at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:218)
at org.eclipse.jdt.internal.core.JavaProject.getJavaProjectElementInfo(JavaProject.java:1513) at org.eclipse.jdt.internal.core.JavaProject.newNameLookup(JavaProject.java:2419)
at org.eclipse.jdt.internal.core.SearchableEnvironment.<init>(SearchableEnvironment.java:60)
at org.eclipse.jdt.internal.core.SearchableEnvironment.<init>(SearchableEnvironment.java:74)
at org.eclipse.jdt.internal.core.JavaProject.newSearchableNameEnvironment(JavaProject.java:2444)
at org.eclipse.jdt.internal.core.Openable.codeSelect(Openable.java:151)
at org.eclipse.jdt.internal.core.CompilationUnit.codeSelect(CompilationUnit.java:314)
at org.eclipse.jdt.internal.core.CompilationUnit.codeSelect(CompilationUnit.java:308)
at org.eclipse.jdt.internal.ui.text.java.hover.AbstractJavaEditorTextHover.getHoverInfo(AbstractJavaEditorTextHover.java:110)
at org.eclipse.jdt.internal.ui.text.java.hover.BestMatchHover.getHoverInfo(BestMatchHover.java:102)
at org.eclipse.jdt.internal.ui.text.java.hover.JavaEditorTextHoverProxy.getHoverInfo(JavaEditorTextHoverProxy.java:69)
at org.eclipse.jface.text.TextViewerHoverManager$4.run(TextViewerHoverManager.java:160)

has any one already started using gpd-3.0.6???
I am using
ECLIPSE : eclipse-SDK-3.1-linux
JAVA : jdk 1.5.0
GPD : jbpm-gpd-3.0.6
JBoss jbpm 3.0.2

Thanks and Regards

[koen.aers]

This is a known issue. Apologies for not communicating this thoroughly. There is a slight incompatibility between the 3.0.x branch of core jbpm installations and the 3.1 branch starting with beta1.
To patch this incompatibility you should do the following :

1. Locate the folder 'src/resources/gpd' in the core jbpm installation you are trying to use in your project. If this folder does not exist, create it.
2. In this folder, create a file named 'version.info.xml'
3. For version 3.0.2 of jbpm the contents of this file should be the following :

<jbpm-version-info name="jbpm-3.0.2"
 namespace="http://jbpm.org/3/jpdl">

 <classpathentry path="lib/jbpm/jbpm-3.0.2.jar" src="src" />
 <classpathentry path="lib/jbpm/jbpm-identity-3.0.2.jar" src="src" />

 <classpathentry path="lib/dom4j/dom4j-1.6.1.jar" />
 <classpathentry path="lib/ant/ant-1.6.2-stripped.jar"/>
 <classpathentry path="lib/jboss/javax.servlet.jar"/>
 <classpathentry path="lib/junit/junit-3.8.1.jar"/>
 <classpathentry path="lib/hibernate/ehcache-1.1.jar"/>
 <classpathentry path="lib/hibernate/jdbc2_0-stdext.jar"/>
 <classpathentry path="lib/hibernate/jta.jar"/>
 <classpathentry path="lib/jboss/jboss.jar"/>
 <classpathentry path="lib/jboss/jboss-jmx.jar"/>
 <classpathentry path="lib/jboss/jboss-system.jar"/>
 <classpathentry path="lib/jboss/jboss-common.jar"/>
 <classpathentry path="lib/jsf/jstl-1.1.0.jar"/>
 <classpathentry path="lib/jsf/standard-1.1.2.jar"/>
 <classpathentry path="lib/jboss/hsqldb.jar"/>
 <classpathentry path="lib/jboss/javax.servlet.jsp.jar"/>
 <classpathentry path="lib/jboss/jboss-j2ee.jar"/>
 <classpathentry path="lib/jboss/antlr-2.7.5H3.jar"/>
 <classpathentry path="lib/jboss/asm.jar"/>
 <classpathentry path="lib/jboss/asm-attrs.jar"/>
 <classpathentry path="lib/jboss/bsh-1.3.0.jar"/>
 <classpathentry path="lib/jboss/cglib-2.1_2jboss.jar"/>
 <classpathentry path="lib/jboss/commons-collections.jar"/>
 <classpathentry path="lib/jboss/commons-logging.jar"/>
 <classpathentry path="lib/jboss/log4j.jar"/>
 <classpathentry path="lib/jboss/xercesImpl.jar"/>
 <classpathentry path="lib/jboss/xml-apis.jar"/>
 <classpathentry path="lib/jsf/myfaces-api.jar"/>
 <classpathentry path="lib/jsf/myfaces-impl.jar"/>
 <classpathentry path="lib/hibernate/jaxen-1.1-beta-4.jar"/>

</jbpm-version-info>

4. Let us know if this works.

Regards,
Koen

[forjbpm]

Hi Koen,

Thank a lot for answering my question even on Sunday.

Please confirm following steps:
1. in my core jbpm installation (jbpm-starters-kit-3.0.2 /jbpm) i had to create gpd folder in jbpm/src/resorces.
2. I created file name with version.info.xml as per your instructions.
But it didnt work for me atleast.

I could locate one more version.info.xml file. ( Is this the one you meant??)
*eclipse/plugins/org.jbpm.core_3.0.6/src/resources/gpd/version.info.xml*
was pointing to

jbpm-3.1-beta1

I corrected this file(also) as per your instructions.

But this thing also didnt correct my problem.

Thanks and Regards

[forjbpm]

Do you think that I should update to jbpm-3.1-beta1 version?
Thanks and Regards

[koen.aers]

The file should reside in 'jbpm/src/resources/gpd'. And you should make sure that in your JBoss jBPM preferences page the right Core Eclipse installation is referenced.
Updating the included version.info.xml will not help indeed.
If you can update to jBPM 3.1, you definitely should...

Regards,
Koen