Spring Boot Process Applications are deployed to the default Spring Boot engine if no engine is available in processes.xml

XMLWordPrintable

      Scenario 1:

      <process-application
  xmlns="http://www.camunda.org/schema/1.0/ProcessApplication"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

  <process-archive name="loan-approval">
    <process-engine>default</process-engine>
    <properties>
      <property name="isDeleteUponUndeploy">false</property>
      <property name="isScanForProcessDefinitions">true</property>
    </properties>
  </process-archive>
</process-application>

      Current & Expected Behavior:
      The Process Application should be deployed to the Process Engine with name default or throw a "no such process engine exists" exception.

      Scenario 2:

      <process-application
  xmlns="http://www.camunda.org/schema/1.0/ProcessApplication"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

  <process-archive name="loan-approval">
    <properties>
      <property name="isDeleteUponUndeploy">false</property>
      <property name="isScanForProcessDefinitions">true</property>
    </properties>
  </process-archive>
</process-application>

      Current Behavior:
      The Process Application deployment throws a "no such process engine exists" exception.

      Expected Behavior:
      The Process Application should be deployed to the Process Engine available in the Spring Boot application.

            Assignee:
            Yana Vasileva
            Reporter:
            Nikola Koevski
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: