Difference between revisions of "GxRest"
From Gcube Wiki
Manuele.simi (Talk | contribs) |
Manuele.simi (Talk | contribs) |
||
| Line 3: | Line 3: | ||
The library is consistently divided in: | The library is consistently divided in: | ||
* context-aware requests sent from a client to a web application | * context-aware requests sent from a client to a web application | ||
| − | * outbound status-aware [GxRest/Responses#Outbound_Responses responses] returned from a web application | + | * outbound status-aware [[GxRest/Responses#Outbound_Responses | responses]] returned from a web application |
| − | * inbound [GxRest/Responses#Inbound_Responses responses] received by a client. | + | * inbound [[GxRest/Responses#Inbound_Responses | responses]] received by a client. |
Besides independence over the web framework, the most important features of the library are: | Besides independence over the web framework, the most important features of the library are: | ||
* to abstract of the HTTP-based details required by the gCube framework when invoking a remote service | * to abstract of the HTTP-based details required by the gCube framework when invoking a remote service | ||
* 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. | * 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. | ||
Revision as of 16:45, 15 February 2018
The gCube eXtensions to the Rest Protocol library (gxRest) provides a convenient round-trip interaction between a Restful web application and its client. The approach is completely independent from the web framework used to develop the web application, being entirely based on the javax.ws.rs package.
The library is consistently divided in:
- context-aware requests sent from a client to a web application
- outbound status-aware responses returned from a web application
- inbound responses received by a client.
Besides independence over the web framework, the most important features of the library are:
- to abstract of the HTTP-based details required by the gCube framework when invoking a remote service
- 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.
