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

When embedding the engine jar, the default job executor does not exist when I use a processes.xml file

    XMLWordPrintable

Details

    • Bug Report
    • Resolution: Fixed
    • L3 - Default
    • 7.0.0-alpha3, 7.0.0
    • None
    • engine, tasklist
    • None

    Description

      Example: Tasklist development setup (maven tomcat7:run-war -Pdevelop) embeds the engine jar.
      It does not work because its processes.xml declares a new engine that references the default job executor. However, this job executor does not exist.

      Also, it is not possible to declaratively create a job executor in processes.xml.

      mgm-controller-panel

        This is the controller panel for Smart Panels app

        Attachments

          Issue Links

            is related to

            Feature Request - A new feature of the product, which has yet to be developed. CAM-678 As PA DEV, I can provide a custom processes.xml file location in @ProcessApplication

            • L3 - Default - Minor issue or issue with existing workaround, feature requests and questions
            • Closed

            Activity

              People

                meyer Daniel Meyer
                thorben.lindhauer Thorben Lindhauer
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Salesforce