@yana.vasileva Thanks for the reply. But in my scenario, there is already a camunda installation with a process engine defined and some wars already deployed in a tomcat container.
Now to this tomcat I want to add the war which contains only my processes and service tasks. I do not want to embed the process engine in my war. This is possible with normal spring integration and am wondering if there is a way to do with spring boot as well. May be it is just configuration somewhere but I couldn’t figure out.
I am sorry, I didn’t get the whole picture in the first place.
So if you need only war with the process and java delegates, etc.
You can follow this guide and adjust the project to be spring boot (for example change the build plugins in the pom.xml).
Ok. I get the idea now. So, I should not depend on the spring-boot-starters for camunda and rather just add the required spring-boot dependencies directly to camunda.
I will give it a try. My only doubt is that in this page – https://docs.camunda.org/get-started/spring/shared-process-engine/ – it is clearly mentioned how to make the appropriate modifications to applicationContext.xml so that the SpringServletProcessApplication picks the shared process engine.
Wondering how such changes - if any - should be made when I want spring boot capabilities.
I search a lot and found the same question raised by you. I am trying the same thing which you were asking. Make springboot project using shared engine rather than embedded.
Have you find any solution, can you please guide me to make spring boot application using a shared engine.