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

Incorporate CE SDK into Kogito Runtimes

    XMLWordPrintable

Details

    • False
    • None
    • False
    • 0
    • 0% 0%
    • Hide
      Breaking changes:

      - If using events, the dependecy in the pom should be kogito-events-core and not kogito-events-api plus kogito-services
      - EventReceiver and EventUnmarshaller interfaces has been changed. Examples has been updated accordingly.
      Show
      Breaking changes: - If using events, the dependecy in the pom should be kogito-events-core and not kogito-events-api plus kogito-services - EventReceiver and EventUnmarshaller interfaces has been changed. Examples has been updated accordingly.
    • ---
    • ---
    • 2022 Week 38-40 (from Sept 19)

    Description

      Currently, we have a few classes doing the precisely same feature that the CE SDK is already covering.

      To increase the reliability and maintainability of our core APIs, it's worth leveraging a widespread library used by many other projects.

      Attachments

        Issue Links

          is depended on by

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) KOGITO-8081 EventDrivenQueryExecutor to accept DataEvent rather than CloudEvent

          • 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.
          • Resolved
          is incorporated by

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. SRVLOGIC-50 [feature] Adopt CloudEvent SDK for new Event API

          • 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 related to

          Feature Request - Feature requests from customers and/or users KOGITO-8068 Change default event marshaller/unmarshallers per channel

          • 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.
          • Resolved
          relates to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) KOGITO-7680 Data Content Type for produced events on workflows should be populated to facilitate integrations in the platform

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved

          Activity

            People

              ftirados Francisco Javier Tirado Sarti
              rhn-support-zanini Ricardo Zanini Fernandes
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: