Just checking if we could use “Relative Context Path” for the deployment in Camunda?
When we build the app with Spring Boot, Camunda resources are mapped on /app, /api and /lib.
There must be a possibility to put the resources under another context. E.g. /camunda/api, /camunda/app etc.
Ideally, this “camunda” context path must be configurable.
Implementation hints:
Most probably Spring Boot packages all web resources together under one context, when deploying them on embedded Tomcat. We could research, if its possible to separate them somehow.
@thorben: When we build the app with Spring Boot, Camunda resources are mapped on /app, /api and /lib.
There must be a possibility to put the resources under another context. E.g. /camunda/api, /camunda/app etc.
Ideally, this “camunda” context path must be configurable.
Implementation hints:
Most probably Spring Boot packages all web resources together under one context, when deploying them on embedded Tomcat. We could research, if its possible to separate them somehow.
Hm, since the JIRA issue CAM-8302 you copied the text from is still unresolved and a couple of people have looked into this already, I don’t see how this can be achieved currently. The ticket is currently not scheduled for implementation, but we are always happy to receive contributions.