Spring/spring-hateoas-examples
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Polishing

Browse Source
This commit is contained in:
Greg Turnquist
2019-07-30 12:18:53 -05:00
parent 6ab1d7f571
commit 06c9c0ac3c
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
basics/README.adoc
View File

@@ -82,13 +82,13 @@ operations.
In REST, the "thing" being linked to is a *resource*. Resources provide both information as well as information on _how_ to
retrieve and update that information.
Spring HATEOAS defines a generic `Resource<T>` container that lets store any domain object (`Employee` in this example), and
Spring HATEOAS defines a generic `EntityModel<T>` container uased to model resources that lets store any domain object (`Employee` in this example), and
add additional links.
IMPORTANT: Spring HATEOAS's `Resource` and `Link` classes are *vendor neutral*. HAL is thrown around a lot, being the
IMPORTANT: Spring HATEOAS's `EntityModel` and `Link` classes are *vendor neutral*. HAL is thrown around a lot, being the
default media type, but these classes can be used to render any media type.
A common convention is to create a factory used to convert `Employee` objects into `Resource<Employee>` objects. Spring
A common convention is to create a factory used to convert `Employee` objects into `EntityModel<Employee>` objects. Spring
HATEOAS provides `SimpleIdentifiableResourceAssembler<T>` as the simplest mechanism to perform these conversions.
[source,java]