java.lang.ClassNotFoundException - Workpoint cannot find custom jars/classes

Document ID : KB000054512
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

Customers using Workpoint workflow are usually writing their own classes and wrap them in their own jars. While they are in the class path, Workpoint does not seem to find these classes/jars and gives out an error instead which resembles:

"Exception caught when executing Java class: Command = '#Fri Apr 04 12:46:42
EDT 2008 MethodIsStatic=false
Method=wfExec
JavaClass=com.ca.test.class.package';
nested exception is:
java.lang.ClassNotFoundException: com.ca.test.class.package"

Solution:

In order for Workpoint to be aware of the custom code classes and jars, the Workpoint CLASSPATH should be edited accordingly. You can find how to perform this both in the IM manuals, and also in the Workpoint documentation under <IM_TOOLS>\Workpoint\docs\designer\JavaExampleJava.htm.

The documentation states to edit workpoint-server.properties files with the location of the custom classes/jars.
Please note that if there is a white space in the path name, the path might be ignored. For example: 'C:\Program Files\My Jars' might not work, however 'C:\MyJars' will work.

You also can try and encapsulate the path with the white space with quotes "C:\Program Files\My Jars"