Uploaded image for project: 'REST Client'
  1. REST Client
  2. MGNLRESTCL-146

Refactor DefaultRestClient invocation, parameterization and error-handling

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Neutral Neutral
    • 2.0
    • 2.0
    • API
    • None
    • 6.2 Ramp-up 19, 6.2 Ramp-up 20
    • 5

      Current DefaultRestClient impl has several indirections from invoke methods to one another, up to a chain of delegation involving 2 public methods + 2 private methods, all responsible for various aspects of building the invocation (invocation itself, parameterization, error-handling).

      Proposing to address that while expanding RestClient's invoke capabilities to take (optionally) an error-handler, passed from the consumer (knowing best what to do then).

      At the same time, we reckon #invoke method accepting whole request body as argument needs to go, in favor of declared bodies in rest calls, and support for template values there.

      restfn may as well accept an error-handler.

        Acceptance criteria

              mgeljic Mikaël Geljić
              mgeljic Mikaël Geljić
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Task DoD

                    Estimated:
                    Original Estimate - Not Specified
                    Not Specified
                    Remaining:
                    Time Spent - 1d 6.5h Remaining Estimate - 0.25d
                    0.25d
                    Logged:
                    Time Spent - 1d 6.5h Remaining Estimate - 0.25d
                    1d 6.5h