Difference between revisions of "GxRest/GxJRS"
From Gcube Wiki
Manuele.simi (Talk | contribs) (→Scope and Features) |
Manuele.simi (Talk | contribs) (→Correlation with the JAX-RS runtime) |
||
Line 15: | Line 15: | ||
* Outbound status-aware [[GxRest/GxJRS/Responses#Outbound_Responses | responses]] returned from a web application. | * Outbound status-aware [[GxRest/GxJRS/Responses#Outbound_Responses | responses]] returned from a web application. | ||
* Inbound [[GxRest/GxJRS/Responses#Inbound_Responses | responses]] received by a client. | * Inbound [[GxRest/GxJRS/Responses#Inbound_Responses | responses]] received by a client. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
= Distribution = | = Distribution = |
Revision as of 16:49, 1 April 2019
Scope and Features
gxJRS is much more advanced than gxHTTP and offers fully-fledged extensions built on top of JAX-RS and gxHTTP.
Prominent features of gxJRS are:
- to achieve independence from the web framework used to develop the web application;
- to guarantee the correctness of requests/responses across the D4Science infrastructure;
- to abstract over the HTTP-based details required by the gCube framework when invoking a remote service;
- to avoid that each service implements its own conventions over the returned responses;
- to return error responses at the familiar (for any Java programmer) level of exceptions and error codes, while web frameworks usually just let return an HTTP status, headers and streams.
Requests
Context-aware requests sent from a client to a web application.
Responses
- Outbound status-aware responses returned from a web application.
- Inbound responses received by a client.
Distribution
gxJRS is available as Maven artifact and can be added to a maven-based project with the following dependency:
<dependency> <groupId>org.gcube.common</groupId> <artifactId>gxJRS</artifactId> <version>LATEST</version> </dependency>