Uploaded image for project: 'Kogito'
  1. Kogito
  2. KOGITO-5621

ProcessConfig is being generated despite the project having a single BPMN file

XMLWordPrintable

    • False
    • False
    • Undefined
    • Hide
      1. Create a new  Kogito SB project
      2. Add a DRL or DMN file to it
      3. Add the Decision or Rule starter in the pom.xml
      4. Compile

      You should see a compilation error in the ProcessConfig file.

      Show
      Create a new  Kogito SB project Add a DRL or DMN file to it Add the Decision or Rule starter in the pom.xml Compile You should see a compilation error in the ProcessConfig file.

      This looks like a pretty critical bug. On Spring Boot (investigation on Quarkus needed), the file ProcessConfig is being generated despite the project having a BPMN file on it. 

      By introducing the new starters (KOGITO-5444), we updated the examples to have a specific engine. So a DMN example, would have only kogito-decisions-spring-boot-starter. See: https://github.com/kiegroup/kogito-examples/tree/1.9.0.Final/decisiontable-springboot-example

      In this example, even though there is no BPMN whatsoever, the jbpm-flow dependency still needs to be added to compile the generated ProcessConfig.

      This file should not be added in this context. If it requires it somehow, the jbpm-flow then should be part of the Decisions Starter. Same thing happens for the Rules Starter. See https://github.com/kiegroup/kogito-examples/tree/1.9.0.Final/ruleunit-springboot-example

              cnicolai@redhat.com Cristiano Nicolai (Inactive)
              rhn-support-zanini Ricardo Zanini
              Marian Macik Marian Macik
              Marian Macik Marian Macik
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: