diff --git a/documentation/blog/en/07-advanced-features-on-developers-portal.md b/documentation/blog/en/07-advanced-features-on-developers-portal.md index b972ddfdd..ae3adfe5b 100644 --- a/documentation/blog/en/07-advanced-features-on-developers-portal.md +++ b/documentation/blog/en/07-advanced-features-on-developers-portal.md @@ -51,7 +51,7 @@ Each code block is then rendered as an individual tab within the ` io.evitadb evita_test_support - 0.6-SNAPSHOT + 2024.2.2 test ``` diff --git a/documentation/user/en/get-started/query-our-dataset.md b/documentation/user/en/get-started/query-our-dataset.md index 037559f35..65e64d616 100644 --- a/documentation/user/en/get-started/query-our-dataset.md +++ b/documentation/user/en/get-started/query-our-dataset.md @@ -129,7 +129,26 @@ thousands of products. ## Connect the Java client -Open your Java IDE and create an evita_external_api/evita_external_api_grpc/client/src/main/java/io/evitadb/driver/EvitaClient.java +Open your Java IDE and add the following dependency to your project: + + + +```Maven + + io.evitadb + evita_java_driver + 2024.2.2 + +``` + + +```Gradle +implementation 'io.evitadb:evita_java_driver:2024.2.2' +``` + + + +Then, create an evita_external_api/evita_external_api_grpc/client/src/main/java/io/evitadb/driver/EvitaClient.java instance: @@ -264,4 +283,4 @@ If you need more hints for querying the data, try [the query API chapter](../use - \ No newline at end of file + diff --git a/documentation/user/en/get-started/run-evitadb.md b/documentation/user/en/get-started/run-evitadb.md index c5161d68b..0c0748a64 100644 --- a/documentation/user/en/get-started/run-evitadb.md +++ b/documentation/user/en/get-started/run-evitadb.md @@ -63,14 +63,14 @@ To integrate evitaDB into your project, use the following steps: io.evitadb evita_db - 10.1.1 + 2024.2.2 pom ``` ```Gradle -implementation 'io.evitadb:evita_db:2024.1.3' +implementation 'io.evitadb:evita_db:2024.2.2' ``` @@ -108,14 +108,14 @@ exception when you enable the corresponding API in evitaDB's configuration. io.evitadb evita_external_api_grpc - 10.1.1 + 2024.2.2 pom ``` ```Gradle -implementation 'io.evitadb:evita_external_api_grpc:2024.1.3' +implementation 'io.evitadb:evita_external_api_grpc:2024.2.2' ``` @@ -128,14 +128,14 @@ implementation 'io.evitadb:evita_external_api_grpc:2024.1.3' io.evitadb evita_external_api_graphql - 10.1.1 + 2024.2.2 pom ``` ```Gradle -implementation 'io.evitadb:evita_external_api_graphql:2024.1.3' +implementation 'io.evitadb:evita_external_api_graphql:2024.2.2' ``` @@ -148,14 +148,14 @@ implementation 'io.evitadb:evita_external_api_graphql:2024.1.3' io.evitadb evita_external_api_rest - 10.1.1 + 2024.2.2 pom ``` ```Gradle -implementation 'io.evitadb:evita_external_api_rest:2024.1.3' +implementation 'io.evitadb:evita_external_api_rest:2024.2.2' ``` diff --git a/documentation/user/en/use/api/write-tests.md b/documentation/user/en/use/api/write-tests.md index 3f29c33e7..b127fe2b2 100644 --- a/documentation/user/en/use/api/write-tests.md +++ b/documentation/user/en/use/api/write-tests.md @@ -44,14 +44,14 @@ artifact into your project: io.evitadb evita_test_support - 10.1.1 + 2024.2.2 test ``` ```Gradle -implementation 'io.evitadb:evita_test_support:2024.1.3' +implementation 'io.evitadb:evita_test_support:2024.2.2' ``` @@ -378,4 +378,4 @@ you'd need a special cleanup procedure for your shared objects, and you might ap
Defines name of the associated dataset.
- \ No newline at end of file + diff --git a/documentation/user/en/use/connectors/java.md b/documentation/user/en/use/connectors/java.md index 861ba7c77..3ab540be9 100644 --- a/documentation/user/en/use/connectors/java.md +++ b/documentation/user/en/use/connectors/java.md @@ -22,6 +22,25 @@ So none of these topics will be covered here. ## Java remote client +In order to use a Java remote client you need only to add following dependency to your project: + + + +```Maven + + io.evitadb + evita_java_driver + 2024.2.2 + +``` + + +```Gradle +implementation 'io.evitadb:evita_java_driver:2024.2.2' +``` + + + Java remote client builds on top of the [gRPC API](./grpc.md). The evita_external_api/evita_external_api_grpc/client/src/main/java/io/evitadb/driver/EvitaClient.java is thread safe and only single instance of it is expected to be used in the application. The client internally manages a pool of gRPC connections to handle parallel communication with the server. @@ -223,7 +242,7 @@ needs to be added as dependency: one.edee.oss proxycian_bytebuddy - 1.3.10 + 1.4.0 ``` @@ -333,4 +352,4 @@ Now we can use the interfaces described above in the following way: The sealed/open principle is a bit more complex than the naive approach of using a single interface for both reading and writing data, but it clearly separates the read and write scenarios, allowing you to maintain control over mutations and their visibility in a multi-threaded environment. - \ No newline at end of file +