https://github.com/epadronu/rest-tools-collections-for-java
[Mirror] At the moment of its conception, this project is for learning purposes. The idea is for me to experiment with authentic RESTful APIs in Java.
https://github.com/epadronu/rest-tools-collections-for-java
hateoas http hypermedia java rest uir
Last synced: 9 months ago
JSON representation
[Mirror] At the moment of its conception, this project is for learning purposes. The idea is for me to experiment with authentic RESTful APIs in Java.
- Host: GitHub
- URL: https://github.com/epadronu/rest-tools-collections-for-java
- Owner: EPadronU
- License: apache-2.0
- Created: 2020-07-10T15:40:37.000Z (over 5 years ago)
- Default Branch: master
- Last Pushed: 2020-10-04T15:15:29.000Z (over 5 years ago)
- Last Synced: 2025-02-25T08:52:59.041Z (about 1 year ago)
- Topics: hateoas, http, hypermedia, java, rest, uir
- Homepage: https://gitlab.com/EPadronU/rest-tools-collections-for-java
- Size: 76.2 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# REST tools collection for Java (RTC4J)
## About this project
At the moment of its conception, this project is for learning purposes. The
idea is for me to experiment with authentic
[**RESTful**](https://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm)
APIs conformed by its three foundational componentes: HTML (Hypermedia), HTTP,
and URI.
To achieve this, I hope for developing a truly RESTful API with no versioning
but still capable of evolving over time, one that offers more than just
[CRUD](https://en.wikipedia.org/wiki/Create,_read,_update_and_delete)
operations without mutating into a
[XML-RPC](https://en.wikipedia.org/wiki/XML-RPC) service, and agnostic of the
chosen data-interchange format.
Additionally, I have the intention to create the bases of a flexible and
adaptable client with a fluent interface for **_browsing_** any RESTful API.
Such a client will be complemented by a domain-specific wrapper, that will be
auto-generated from the API schema, in order to leverage the concrete types and
actions the API exposes in a type-safe way.
Thus, this project will serve as an umbrella for all the tools I hope for
developing with the help of the Java ecosystem in order to achieve the above
goals.
## License
The source code for every single component/tool developed for this project will
be under the [Apache License, Version
2.0](https://www.apache.org/licenses/LICENSE-2.0).