[MGNLRESTCL-64] Implement minimal PoC that consumes subset of the OpenAPI spec and configures rest client Created: 18/Jul/19  Updated: 16/Sep/19  Resolved: 27/Aug/19

Status: Closed
Project: REST Client
Component/s: None
Affects Version/s: None
Fix Version/s: 2.0

Type: Task Priority: Neutral
Reporter: Jaroslav Simak Assignee: Quach Hao Thien
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: 4.5h
Time Spent: 16d 6.5h
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLRESTCL-57 Investigate leveraging OpenAPI schemas Closed
dependency
is depended upon by MGNLRESTCL-66 Productise outcome of POC - (config r... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Epic Link: Declarative REST clients
Sprint: Declarative REST 2, Declarative REST 3, Declarative REST 4, Declarative REST 5
Story Points: 13

 Description   

thien.quach presented the OpenAPI spec. As a conclusion of his investigation we decided to implement PoC that will consume the spec and will configure rest client (including rest calls).

PoC should showcase that we are able to consume & transform the spec and should also include some example rest calls.

Some notes from the presentation:

  • Find a semi-popular or test service exposing an OpenAPI schema
  • Check for Open API processors? support in Jersey/RESTEasy?
  • Evaluate self-made conversion from OpenAPI to our current definitions
    • vs. inferring basic GET calls from a consumer implementation
    • e.g. ui-framework-rest
  • Timebox a small PoC

Generated at Mon Feb 12 10:42:51 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.