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

XMLWordPrintable

    • Type: Bug Report
    • Resolution: Fixed
    • Priority: L3 - Default
    • 7.0.0-alpha3, 7.0.0
    • Affects Version/s: None
    • Component/s: engine, tasklist
    • None

      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.

        This is the controller panel for Smart Panels app

              Assignee:
              Daniel Meyer
              Reporter:
              Thorben Lindhauer
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: