I run flowable-task by using flowable/all-in-one:6.4.1 docker image. I published a new process which contains many service tasks in it, and put my JAR under webapps/flowable-task/WEB-INF/lib. It works very well when running.
However, if I did the following steps …
- Move my JAR out of webapps/flowable-task/WEB-INF/lib
- Restart flowable/all-in-one container
- Put my JAR into webapps/flowable-task/WEB-INF/lib back
- Use API “/flowable-task/process-api/runtime/process-instances” to init my process instance
At the last step, it will report “couldn’t instantiate class xxx.xxx.xxx” due to “Class not found”. The only way to solve this is to restart flowable/all-in-one container again.
I think I should publish any new process and JAR when Flowable is running, and the new process and JAR can work without restart Flowable, right?
Why need I restart Flowable in this case?