Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-8302

Camunda boot within own context

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Duplicate
    • Icon: L3 - Default L3 - Default
    • None
    • None
    • spring-boot, webapp
    • None

      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.

      Issue originated from here: https://github.com/camunda/camunda-bpm-spring-boot-starter/issues/150

        This is the controller panel for Smart Panels app

            [CAM-8302] Camunda boot within own context

            Jan Galinski added a comment -

            I think a good entrypoint for discussion would be: what would we do, if we wanted to serve a custom html5/rest application from within the camunda webapp war.
            I think the way the camunda webapp application is designed this is not easily possible so far and if we solve it, it should also work on spring boot.

            Jan Galinski added a comment - I think a good entrypoint for discussion would be: what would we do, if we wanted to serve a custom html5/rest application from within the camunda webapp war. I think the way the camunda webapp application is designed this is not easily possible so far and if we solve it, it should also work on spring boot.

            Frank Jakop added a comment -

            Ideally I would think you should separate the process engine and the frontend, so that we could serve the engine as a service behind an API gateway and just serve the frontend on the gateway or a different server allowing to choose a context url deliberately.

            Frank Jakop added a comment - Ideally I would think you should separate the process engine and the frontend, so that we could serve the engine as a service behind an API gateway and just serve the frontend on the gateway or a different server allowing to choose a context url deliberately.

            Thorben Lindhauer added a comment - - edited

            This has been solved with CAM-11373 which will be released with 7.13.0.

            Note that technically the solution does not move the Camunda resources into its own servlet context, but rather ensures that the Camunda resources have dedicated sub path in Spring Boot's default context.

            Thorben Lindhauer added a comment - - edited This has been solved with CAM-11373 which will be released with 7.13.0. Note that technically the solution does not move the Camunda resources into its own servlet context, but rather ensures that the Camunda resources have dedicated sub path in Spring Boot's default context.

              Unassigned Unassigned
              svetlana.dorokhova Svetlana Dorokhova
              Votes:
              11 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: