Hello,
Thanks for the clarification.
Indeed I mixed the two, because I’m not sure I really understand what this concept of app can be used for outside of the UI applications. But I don’t really intend to use it, so it’s not an issue.
I managed to start the admin UI pointing to REST services in my main app, so for the admin UI I think we will reuse it, it’s sufficient for a start.
For information, in case it’s useful for someone, I have 3 components:
- My main JVM containing the engines, the REST services, the autodeployed processes/…
- And the admin + idm wars, unchanged, but with the externalized java property SPRING_APPLICATION_JSON so that they point to the right REST services (+ in addition to the DB config).
Concerning the Task UI, my opinion is that it could indeed be helpful if it could use other external REST services from the main app, instead of embedding everything, because for internal use only it could also have been sufficient for a first version (but there was already a thread about this… see https://forum.flowable.org/t/make-task-ui-a-rest-client-rather-than-server/457/7 ). But we will redevelop I guess.
Thank you for your help,
Sophie