We couldn't load the project sidebar. Refresh the page to try again.
If the problem persists, contact your Jira admin.
Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-12910 Integrate Scala DMN Engine
  3. CAM-12920

In DMN Wrapper, support current DmnEngine interface

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Unresolved
    • Icon: L3 - Default L3 - Default
    • None
    • None
    • scala-dmn
    • None

      AT

      • In DMN Wrapper, support current DmnEngine interface
      • Add support for DmnDecisionTableResult result types (currently converted in process engine based on legacy engine implementation)
      • Add tests that ensure that behavior between the legacy and the Scala DMN Engine is the same

      Reasoning

      • The offering of the legacy DMN Engine includes a Java-friendly API to operate the DMN Engine decoupled from the Process Engine in a standalone manner
      • One could say users who want to continue using the Standalone DMN Engine should switch to the Scala DMN Engine
        • However, our community consists mainly of Java enthusiasts who might have problems to integrate a Scala library into their projects
        • By implementing the existing DmnEngine interface for the Scala DMN Engine, we can continue to provide a Java-based standalone option for our users
      • Wrapping the DmnEngine interface around the Scala Engine makes migrating from the legacy standalone DMN Engine more smooth

      See

        This is the controller panel for Smart Panels app

            Loading...
            Uploaded image for project: 'camunda BPM'
            1. camunda BPM
            2. CAM-12910 Integrate Scala DMN Engine
            3. CAM-12920

            In DMN Wrapper, support current DmnEngine interface

            XMLWordPrintable

              • Icon: Sub-task Sub-task
              • Resolution: Unresolved
              • Icon: L3 - Default L3 - Default
              • None
              • None
              • scala-dmn
              • None

                AT

                • In DMN Wrapper, support current DmnEngine interface
                • Add support for DmnDecisionTableResult result types (currently converted in process engine based on legacy engine implementation)
                • Add tests that ensure that behavior between the legacy and the Scala DMN Engine is the same

                Reasoning

                • The offering of the legacy DMN Engine includes a Java-friendly API to operate the DMN Engine decoupled from the Process Engine in a standalone manner
                • One could say users who want to continue using the Standalone DMN Engine should switch to the Scala DMN Engine
                  • However, our community consists mainly of Java enthusiasts who might have problems to integrate a Scala library into their projects
                  • By implementing the existing DmnEngine interface for the Scala DMN Engine, we can continue to provide a Java-based standalone option for our users
                • Wrapping the DmnEngine interface around the Scala Engine makes migrating from the legacy standalone DMN Engine more smooth

                See

                  This is the controller panel for Smart Panels app

                        Unassigned Unassigned
                        tassilo.weidner Tassilo Weidner
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        2 Start watching this issue

                          Created:
                          Updated:

                              Unassigned Unassigned
                              tassilo.weidner Tassilo Weidner
                              Votes:
                              0 Vote for this issue
                              Watchers:
                              2 Start watching this issue

                                Created:
                                Updated: