easy and clean support for camunda REST api via starter about camunda-bpm-spring-boot-starter

I think we should stick to Jersey

On 09.09.15 11:30, Jan Galinski wrote:

The current starter supports adding the REST API controllers. The
setup is very complicated, there are a lot of dependencies I have to
add to my pom to activate this and even then it is not perfectly clear
how it all works together and how I can configure it. (see also #20
#20)

Maybe we can find a simpler way by offering a dedicated "starter-rest"
that bundles the usual dependencies to run server+api?

Also we should investigate if we can get rid of the jboss/resteasy
dependency, doesn't seem to be very "springy" in my opinion ...

—
Reply to this email directly or view it on GitHub
#21.

[hawky-4s-]

Forgot: Also provide a simple spring-boot pom which brings the necessary
dependencies. +1

[osteinhauer]

Indeed the dependencies are not really clean. I like the "starter-rest" idea.

Am 09.09.2015 um 11:30 schrieb Jan Galinski [email protected]:

starter-rest

[jangalinski]

Christian introduced the starter-rest which makes live easier. But I do not like that the "starter" module has an optional dep on jersey just to provide a RestConfiguration that will be triggered when using the starter-rest module. So I would move the Rest specific stuff to the new module.

[osteinhauer]

Move the REST specific stuff to the new module including the RestConfigurationclass.

[jangalinski]

I moved all the code and tests and double checked: works!

Question: do we still need the RestConfiguration class? Or is it enough to provide the Camunda JerseyConfig, so the implementing apps can extend it?