DATAREST-811 - Improved documentation mentioning @Version in ETag calculation.

We now explain in detail which @Version annotation to use as it depends on which store is backing the entity.

Original pull request: #295.
This commit is contained in:
Oliver Gierke
2018-07-04 16:31:00 +02:00
parent 3960318d36
commit 29ec187d48

View File

@@ -18,7 +18,7 @@ Consider the following example:
include::{spring-data-rest-root}/spring-data-rest-webmvc/src/test/java/org/springframework/data/rest/webmvc/support/ETagUnitTests.java[tag=versioned-sample]
----
<1> The `@javax.persistence.Version` annotation flags this field as a version marker.
<1> The `@Version` annotation (the JPA one in case you're using Spring Data JPA, the Spring Data `org.springframework.data.annotation.Version` one for all other modules) flags this field as a version marker.
====
The POJO in the preceding example, when served up as a REST resource by Spring Data REST, has an `ETag` header with the value of the version field.