Uploaded image for project: 'Kogito'
  1. Kogito
  2. KOGITO-49

Stunner - [BPMN] Client-Side Marshalling

    XMLWordPrintable

Details

    • client-side-marshalling
    • To Do
    • Medium
    • 100
    • 100% 100%

    Description

      Coordinate effort to migrate BPMN marshallers to the client side.

      High level steps:

      1. Design & PoC (ends once KOGITO-28 is done)
      1. Build & publish cient side compatible EMF support module (KOGITO-51)
      1. Build & publish client side compatible module for BPMN domain model classes (KOGITO-29)
      1. Build & publish client side compatible EMF/XMI support module (KOGITO-31)
      1. Stunner side (KOGITO-52)
        1. Refactor marshalling "Converters" in order to expose code to client side
        2. Achieve end-to-end client side marshalling capabilities, by integrating new modules above

      Some info:

      Attachments

        Issue Links

          incorporates

          Task - Represents a small unit of work that is not end-user facing. KOGITO-28 [Stunner] PoC - Achieve end to end marhalling support

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. KOGITO-29 Build & publish GWT-compatible Eclipse (EMF) models for BPSim, Drools namespaces

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. KOGITO-31 Build & publish the EMF-XMI client side support module

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. KOGITO-51 Build & publish the EMF Core client side support module

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. KOGITO-52 Stunner - [BPMN] Implement client side marshalling support

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is incorporated by

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. KOGITO-50 Pure Client Side BPMN Editors

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              romartin@redhat.com Roger Martinez
              evacchi Edoardo Vacchi (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: