Feature/version 2.2.0

README.md

@@ -47,7 +47,7 @@ clone the repository, import the projects and declare a dependency to either the
 <dependency>
     <groupId>com.sap.olingo</groupId>
     <artifactId>odata-jpa-metadata</artifactId>
-    <version>2.1.3</version>
+    <version>2.2.0</version>
 </dependency>
 ```
 
@@ -57,7 +57,7 @@ Or to the complete processor:
 <dependency>
     <groupId>com.sap.olingo</groupId>
     <artifactId>odata-jpa-processor</artifactId>
-    <version>2.1.3</version>
+    <version>2.2.0</version>
 </dependency>
 ```
 
@@ -103,3 +103,4 @@ Detailed information including third-party components and their licensing/copyri
 |2.1.0| - Enhancement of annotation API<br>- Enhancement of API for server driven paging<br>- Optional support of IN operand <br>- Update to Olingo 5.0.0<br>- Rework $count implementation<br>- Fix problem with $count on collection properties|No|
 |2.1.1| - Fix for issue [#292](https://github.com/SAP/olingo-jpa-processor-v4/issues/292)|No|
 |2.1.3| - Fix for issue [#319](https://github.com/SAP/olingo-jpa-processor-v4/issues/319)<br> - Fix for issue [#325](https://github.com/SAP/olingo-jpa-processor-v4/issues/325)<br> - Fix for issue [#327](https://github.com/SAP/olingo-jpa-processor-v4/issues/327)<br> - Fix for issue [#331](https://github.com/SAP/olingo-jpa-processor-v4/issues/331)<br> - Fix of en issue with $orderby and _to one_ navigation properties |No|
+|2.2.0| - Fix for issue [#378](https://github.com/SAP/olingo-jpa-processor-v4/issues/378)<br>  - Fix for issue [#378](https://github.com/SAP/olingo-jpa-processor-v4/issues/378)<br> - Fix for issue [#361](https://github.com/SAP/olingo-jpa-processor-v4/issues/361)<br> - Fix for issue [#352](https://github.com/SAP/olingo-jpa-processor-v4/issues/352)<br> - Fix for issue [#307](https://github.com/SAP/olingo-jpa-processor-v4/issues/307) <br> - Enhancement according to [#314](https://github.com/SAP/olingo-jpa-processor-v4/issues/314)|No|

additionalWords.directory

@@ -71,3 +71,4 @@ Hana
 Desc
 Crossjoin
 Pageable
+xml

jpa-archetype/odata-jpa-archetype-spring/pom.xml

@@ -4,7 +4,7 @@
 	<parent>
 		<groupId>com.sap.olingo</groupId>
 		<artifactId>odata-jpa-archetype</artifactId>
-        <version>2.2.0-SNAPSHOT</version>
+        <version>2.2.0</version>
 	</parent>
 	<artifactId>odata-jpa-archetype-spring</artifactId>
 	<name>Archetype - odata-jpa-archetype-spring</name>

jpa-archetype/odata-jpa-archetype-spring/src/main/resources/archetype-resources/pom.xml

@@ -17,7 +17,7 @@
 	</parent>
 
 	<properties>
-		<processor.version>2.2.0-SNAPSHOT</processor.version>
+		<processor.version>2.2.0</processor.version>
 		<java.version>17</java.version>
 		<build.sourceEncoding>UTF-8</build.sourceEncoding>
 		<eclipselink.version>4.0.3</eclipselink.version>

jpa-archetype/pom.xml

@@ -4,7 +4,7 @@
     <modelVersion>4.0.0</modelVersion>
     <groupId>com.sap.olingo</groupId>
     <artifactId>odata-jpa-archetype</artifactId>
-    <version>2.2.0-SNAPSHOT</version>
+    <version>2.2.0</version>
     <packaging>pom</packaging>
     <url>https://github.com/SAP/olingo-jpa-processor-v4</url>
 

jpa-tutorial/Questions/HowToBuildServerDrivenPaging.adoc

@@ -1,4 +1,4 @@
-= How to build server driven paging?
+= How to build server-driven paging?
 
 == Introduction
 
@@ -51,7 +51,7 @@ it is worth to read the chapter, as it contains some general hints.
 
 == Single service instance single thread
 
-Implementing server driven paging, we must answer some questions. The first, general question, is how the skip-token should look like. 
+Implementing server-driven paging, we must answer some questions. The first, general question, is how the skip-token should look like. 
 There are two obvious options: 
 
 . The skip-token is a string that contains all the information needed to build the next page and to determine the last page.
@@ -241,7 +241,7 @@ Last step is to implement `getNextPage`:
 <2> Check if this is the last page.
 <3> Calculate the value of $top, which may be different for the last page.
 
-We are done and can test our complete server driven paging.
+We are done and can test our complete server-driven paging.
 
 == Single service instance multiple threads
 
@@ -277,7 +277,7 @@ public class JPAExamplePagingProvider implements JPAODataPagingProvider {
 
 == Multiple service instances
 In case we have multiple instances of our service, the standard situation for microservices, we usually do not know which instance
-will handle a request. It may or may not be the same that has handled the request before. This holds also true for server driven paging.
+will handle a request. It may or may not be the same that has handled the request before. This holds also true for server-driven paging.
 Therefore, we need to make the query information available for all instances, which requires a central backing service 
 that can be reached from each instance of our service. Two options will be described below.