I am looking for the best practices on deploying common java delegates to tomcat. Ideally, we would like to have our own delegates provided central business logic to be used inside any bpm our clients would be designing. We don’t want to put them in a war file like I have seen suggested here (at least I think). We would like to build our delegates and task listeners into some sort of common-core.jar lib and deploy it to the tomcat lib folder so that it would be available to bpm that gets deployed. Won’t matter if it is via rest api or deploying their own war file.
What is the best way to go about this?
Hi @dayv2005,
on Tomact it’s fine to create a jar from the maven project including all the delegate implementations and place it in the lib folder, next to the camunda-engine.jar.
Hope this helps, Ingo
Thanks. I believe this is the approach we will be taking. Wanted to make sure that it was a reasonable approach. Thanks for the help.
I manually created a jar file containing a class that implements the JavaDelegate interface and place it in the lib directory where the camunda-engine.jar file is. Then I restarted the server. But I still get the following error when the process reaches the service task that uses the Java class. What am I doing wrong? Thanks.
An error happened while submitting the task form : Cannot submit task form 60f73cae-ba26-11e9-824c-acde48001122: ENGINE-09008 Exception while instantiating class ‘com/haulmatic/bpm/delegates/XYProcessDelegate.class’: ENGINE-09017 Cannot load class ‘com/haulmatic/bpm/delegates/XYProcessDelegate.class’: com/haulmatic/bpm/delegates/XYProcessDelegate.class