I am new to flowable, I am facing an issue with Java Delegate classes.
I am using flowable-modeler to create and deploy the workflows and I have created a REST API application to to perform different operations on workflow like start, complete etc.
Also i have created separate java application for Java Delegate classes and converting it into jar file and adding as dependency to my REST API application. Now when i call my custom REST api service to start the process, it is starting and picking the delegate class and executing properly.
If i make the service task as Asynchronous, then it is not picking the delegate class and throwing class not found exception.
If i place that jar file in Flowable-task WEB-INF/lib folder , then it is picking java class in both the scenarios. But some times when i change the flow, publish and start the process, then it is throwing class not found exception again.
Can some one please help me, how to avoid placing jar file 2 places every time i change it and also help me to resolve class not found exception.
Do you run 2 flowable engines? That could be reason why you need to place jar into 2 places.
I would recommend to use only one engine instance in this case.
I am creating a process engine in my REST API application. Will flowable-task or any other apps will creates process engine? If that is the case 2 process engines are getting created.
Now my question is, If i don’t create process engine in my REST API, how to access the engine services?
yes flowable-task app starts it’s own flowable engine. Both of them points to the same DB, that’s why they share case/process… instances.
It is fine for ordinary operations, but in the case when both engines have async executor enabled, the first one (the first who executes job query) takes async job from the DB and executes it.
Solution proposals:
enable async executor only on one engine instance.
Sure. Can you please tell me how to use the process engine which is created with flowable-task in my REST API application. with that i can avoid creating 2 process engines and 2 async executors.
I made changes based on your suggestions. When i am trying to call my custom rest api from postman or rest client with basic authentication, it is redirecting to flowable-idm application login page. But when i invoke default flowable rest api with basic authentication, it is working fine. Do i need to make any specific changes to my custom rest controller to work properly with basic authentication.
When i hit custom service URL from post man, it is showing below redirect URL and call is not going to my custom service.
There is no dispatcher implemented in my project. My project is having only REST Controller java class.
I think default flowable-task dispatcher is getting executed. I just want to know is there any other configuration required to redirect to custom REST API after successful authentication.
The reason why you are getting redirected is because you are getting hit by the default security configuration. I would suggest to you to provide configuration (that would kick in before the flowable-task one) and you would configure the authentication for it in there. You can find the flowable-task SecurityConfigurationhere