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

In platform, move legacy implementation into dedicated module

XMLWordPrintable

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

      AT

      In the platform, move legacy implementation classes into a dedicated module, separated from the DMN API.

      Reasoning

      The current Java DMN engine implementation will be replaced by integrating a Scala DMN engine. The API is supposed to stay as-is to still provide compatibility. This API module will be used by the platform wrapper for the Scala DMN engine (CAM-12920) as well to keep the specific implementation transparent to the platform itself. As the current Java implementation will potentially become a legacy implementation (CAM-12925), this should be moved to a separate module using the then cleared-up API module.

        This is the controller panel for Smart Panels app

            [CAM-12924] In platform, move legacy implementation into dedicated module

            Thorben Lindhauer added a comment -

            This ticket was migrated to github: https://github.com/camunda/camunda-bpm-platform/issues/2508. Please use this link for any future references and continue any discussion there.

            Thorben Lindhauer added a comment - This ticket was migrated to github: https://github.com/camunda/camunda-bpm-platform/issues/2508 . Please use this link for any future references and continue any discussion there.

              Unassigned Unassigned
              tobias.metzke Tobias Metzke-Bernstein
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: