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

Packaging REST starter as WAR is not working

    • Icon: Bug Report Bug Report
    • Resolution: Won't Fix
    • Icon: L3 - Default L3 - Default
    • None
    • spring-boot 2.3.0-alpha2
    • spring-boot
    • None

      1. Create a project containing dependency on camunda-bpm-spring-boot-starter-rest and packaging as WAR (see example project attached)
      2. Build and deploy on Tomcat

      Current result:
      1. Errors in Tomcat log (attached)
      2. REST API is not accessible

      Expected result:
      No error and REST API is working

      Workaround would be to add following bean to the project:

      @Component
      @ApplicationPath("/resources")
      public class RESTConfig extends CamundaJerseyResourceConfig {
      
      }
      

      Also see https://github.com/camunda/camunda-bpm-spring-boot-starter/issues/193
      Possible fix is listed in this comment, but this would make useless CamundaBpmRestJerseyAutoConfiguration class and impossible to configure REST endpoints in another way.

        This is the controller panel for Smart Panels app

            [CAM-8414] Packaging REST starter as WAR is not working

            Hi,
            I gave the workarounf a try on version: 3.2.0
            Does not seem to be still working.
            Is there any alternative workaround ?

            Raffaele Esposito added a comment - Hi, I gave the workarounf a try on version: 3.2.0 Does not seem to be still working. Is there any alternative workaround ?

            Thorben Lindhauer added a comment - - edited

            Packaging as WAR is currently not supported, so I am closing this issue.

            Thorben Lindhauer added a comment - - edited Packaging as WAR is currently not supported, so I am closing this issue.

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

                Created:
                Updated:
                Resolved: