REST API Camunda Rest Auto Configuration disable

Camunda 7 Topics Discussion & Questions
1

We have a use case where we need to exclude the Camunda REST API via a Spring profile.
Basically we have a Web and Shell app in one “springboot” jar. There is no way currently of disabling CamundaBpmRestJerseyAutoConfiguration - unlike the WebApp and the ProcessEngine using
–camunda.bpm.enabled=false", "–camunda.bpm.webapp.enabled=false

It would be great if you add a condition to the Bean to also exclude it like in CamundaBpmWebappAutoConfiguration
@ConditionalOnProperty(prefix = WebappProperty.PREFIX, name = “enabled”, matchIfMissing = true)

2

Hi @nedge,

why not simply remove the camunda-bpm-spring-boot-starter-rest artifact from the maven dependencies and use the camunda-bpm-spring-boot-starter only?

Hope this helps, Ingo

3

When we start our web app then the Camunda process engine, cockpit and rest API should be started.
When we start the shell we only want the spring command line shell to run using the internal service API and no Workflow components should be started. Why do we have one jar? Our app is large so we don’t want to have different jars (web and shell)as we often have to upload to customer servers and it is a pain to have basically two jars that are almost identical.

4

I managed to get both web and shell running by defining a simple dummy JerseyApplicationPath Bean
It is not elegant but works!
More elegant would be to add the conditional on CamundaBpmRestJerseyAutoConfiguration just like you have it on CamundaBpmWebappAutoConfiguration

5