10-05-2012 09:47 AM
10-09-2012 04:13 AM
10-24-2012 08:17 AM
What is the "cause" exception of the "could not load class"?
org.activiti.engine.ActivitiException: couldn't instantiate class
Caused by: org.activiti.engine.ActivitiClassLoadingException: Could not load class:
Caused by: java.lang.NoClassDefFoundError: org/activiti/engine/delegate/JavaDelegate
It seems that problem isn't on the visibility of my implementation but on the visibility of the activiti engine libraries. Could be?10-24-2012 10:09 AM
10-24-2012 10:18 AM
Yes, it seems to be the case… Altrough it's strange that activiti-classes itself can't find activiti-classes in the class loader :s
10-24-2012 10:30 AM
10-24-2012 11:15 AM
Beware, the SHARED class loader (libs shared with all web apps) can't access the web-app specific classes (which probably contains the activiti-jar).It's OK, but I'm in a different situation: I search for my jar from the webapp in the shared class loader, but the webapp has the activiti-jar in his class loader.
Make sure the activiti-jar (engine) is available in the SHARED path IF you depend on it…
10-25-2012 04:24 AM
10-26-2012 04:43 AM
Try adding activiti-engine-5.*.jar in the shared class path as well, since YOUR jar-file depends on it.Ok, thanks for your instructions!
10-26-2012 09:02 AM
Try adding activiti-engine-5.*.jar in the shared class path as well, since YOUR jar-file depends on it.After adding the engine jar another exception has been thrown that required also the slf4j jar. Adding slf4j this exception has been thrown
org.activiti.engine.ActivitiException: org.mytest.MyDelegate doesn't implement org.activiti.engine.delegate.JavaDelegate nor org.activiti.engine.impl.pvm.delegate.ActivityBehavior
But the same jar (same file), used in the webapp lib folder run correctly. I don't understand why.
Tags
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.