Uploaded image for project: 'Serverless logic'
  1. Serverless logic
  2. SRVLOGIC-131

Serverless workflow Java fluent API

    XMLWordPrintable

Details

    • Feature
    • Resolution: Unresolved
    • Major
    • 1.33.0
    • 1.30.0
    • Core
    • None
    • False
    • None
    • False
    • 0
    • 0% 0%

    Description

      Although serverless workflow SDK has certain fluent capabilities, it is interesting to complete them by adding an extra layer that allows quick and easy definition of serverless workflow in Java.
      A first working version of the API has been developed, but it lacks, among other things, support for exceptions and compensation. Also, we are awaiting feedback from Parodos team.
      Examples of the usage of the syntax can be found here

      Attachments

        Issue Links

          incorporates

          Feature Request - Feature requests from customers and/or users KOGITO-8855 Add a fluent layer over Serverless Workflow SDK

          • 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

          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-8923 Fluent API. Add possibility to pass FunctionDefinition builder directly to function call

          • 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

          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-8930 Fluent API, rename objectNode and arrayNode to remove ambiguity

          • 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

          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-8934 Fluent API. refactor end method

          • 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

          Activity

            People

              ftirados Francisco Javier Tirado Sarti
              ftirados Francisco Javier Tirado Sarti
              Gonzalo Muñoz Fernández Gonzalo Muñoz Fernández
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: