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

            Tassilo Weidner created issue -
            Tassilo Weidner made changes -
            Link New: This issue is depended on by CAM-12920 [ CAM-12920 ]
            Tassilo Weidner made changes -
            Link New: This issue is depended on by CAM-12925 [ CAM-12925 ]
            Tassilo Weidner made changes -
            Fix Version/s New: 7.15.0 [ 16006 ]
            Tobias Metzke-Bernstein made changes -
            Assignee New: Tobias Metzke-Bernstein [ tobias.metzke ]
            Tobias Metzke-Bernstein made changes -
            Fix Version/s Original: 7.15.0 [ 16006 ]
            Tobias Metzke-Bernstein made changes -
            Description Original: h3. AT

            In platform, move legacy implementation into dedicated module             		New: h3. AT

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

            h3. 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. As the current Java implementation will potentially become a legacy implementation, this should be moved to a separate module using the then cleared-up API module. This API module will be used by the platform wrapper for the Scala DMN engine as well to keep the specific implementation transparent to the platform itself.
            Tobias Metzke-Bernstein made changes -
            Mentioned Roles
            Tobias Metzke-Bernstein made changes -
            Mentioned Groups
            Tobias Metzke-Bernstein made changes -
            Description Original: h3. AT

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

            h3. 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. As the current Java implementation will potentially become a legacy implementation, this should be moved to a separate module using the then cleared-up API module. This API module will be used by the platform wrapper for the Scala DMN engine as well to keep the specific implementation transparent to the platform itself.             		New: h3. AT

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

            h3. 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.
            Tobias Metzke-Bernstein made changes -
            Mentioned Roles
            Tobias Metzke-Bernstein made changes -
            Mentioned Groups

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

                Created:
                Updated: