From 6de00a6dc698d972d925536a2f10ee9beed9ede4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Florian=20L=C3=BCdiger?= Date: Fri, 25 May 2018 14:43:57 +0200 Subject: [PATCH] DATAREST-811 - Fix incorrect @Version documentation. Original pull request: #295. --- src/main/asciidoc/etags-and-other-conditionals.adoc | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/src/main/asciidoc/etags-and-other-conditionals.adoc b/src/main/asciidoc/etags-and-other-conditionals.adoc index da463fa7f..e67691b35 100644 --- a/src/main/asciidoc/etags-and-other-conditionals.adoc +++ b/src/main/asciidoc/etags-and-other-conditionals.adoc @@ -15,10 +15,9 @@ The http://tools.ietf.org/html/rfc7232#section-2.3[ETag header] provides a way t ---- 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> Spring Data Commons's `@Version` annotation flags this field as a version marker. - This POJO, when served up as a REST resource by Spring Data REST, will have an `ETag` header with the value of the version field. We can conditionally `PUT`, `PATCH`, or `DELETE` that resource if we supply a `If-Match` header like this: