[MGNLRESTCL-36] Consider generalizing RESTEasy-specific implementation Created: 26/Nov/18  Updated: 24/Jul/19  Resolved: 24/Jul/19

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

Type: Story Priority: Neutral
Reporter: Mikaël Geljić Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: jaxrs, resteasy
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
supersession
is superseded by MGNLRESTCL-60 Merge resteasy-client module features... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Epic Link: Declarative REST clients

 Description   

REST-client framework-level functionality should not require providing, nor implementing RESTEasy APIs.

REST client libs may be provided on webapp level.


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