refactor: move images of the "api" module to a standard location

The images were stored in the Antora legacy folder (assets/images) and included an extra "images" subfolder. All images are now in the "images" folder of the module.
bonitasoft · Nov 27, 2024 · 90af366 · 90af366
1 parent 66a99bf
commit 90af366
Show file tree

Hide file tree

Showing 8 changed files with 4 additions and 4 deletions.
diff --git a/...ages/images/bdm_model_for_rest_api_01.png → .../api/images/bdm_model_for_rest_api_01.png b/...ages/images/bdm_model_for_rest_api_01.png → .../api/images/bdm_model_for_rest_api_01.png
diff --git a/.../images/images/images-6_0/content-zip.png → modules/api/images/content-zip.png b/.../images/images/images-6_0/content-zip.png → modules/api/images/content-zip.png
diff --git a/...es/images-6_0/dev_overview_api_access.png → ...es/api/images/dev_overview_api_access.png b/...es/images-6_0/dev_overview_api_access.png → ...es/api/images/dev_overview_api_access.png
diff --git a/...images/rest_api_architecture_overview.png → ...images/rest_api_architecture_overview.png b/...images/rest_api_architecture_overview.png → ...images/rest_api_architecture_overview.png
diff --git a/modules/api/pages/bdm-in-rest-api.adoc b/modules/api/pages/bdm-in-rest-api.adoc
@@ -9,7 +9,7 @@ Special attention is paid on performance matters.
 
 Image below shows the BDM model used for the first use-case:
 
-image::images/bdm_model_for_rest_api_01.png[BDM model used]
+image::bdm_model_for_rest_api_01.png[BDM model used]
 
 Note that the relationships from car to wheel1, wheel2, wheel3, wheel4 are *xref:data:define-and-deploy-the-bdm.adoc#lazy_eager_loading[lazy] loaded* (in the Studio, it is
 configured by selecting the `Only load related objects when needed` radio button).

diff --git a/modules/api/pages/create-administration-tools.adoc b/modules/api/pages/create-administration-tools.adoc
@@ -240,7 +240,7 @@ java -Dbonita.home=bonita -jar lib/bonita-cli-1.0.0.jar %*
 
 Build the whole project again. When the build completes, the zip file should contain the following structure:
 
-image::images/images-6_0/content-zip.png[Zip file structure]
+image::content-zip.png[Zip file structure]
 
 Run the appropriate script:
 

diff --git a/modules/api/pages/engine-api-overview.adoc b/modules/api/pages/engine-api-overview.adoc
@@ -68,7 +68,7 @@ The Bonita Engine APIs can be accessed locally or remotely, in the following mod
 * Local: the client accesses the server directly in local mode
 * HTTP&#x3A; the client accesses a remote server via HTTP
 
-image::images/images-6_0/dev_overview_api_access.png[Diagram of API access options]
+image::dev_overview_api_access.png[Diagram of API access options]
 
 The mode you use must be specified in the bonita-client-custom.properties file. By default, the access mode is local. This can be used when the client and engine are using the same JVM. The file contains commented out configurations for remote access modes. To change the mode, simply comment out the configuration for local and uncomment the relevant remote configuration.
 

diff --git a/modules/api/pages/rest-api-overview.adoc b/modules/api/pages/rest-api-overview.adoc
@@ -21,7 +21,7 @@ If your application is using a technology other than Java, you can integrate it
 
 Access to the Web REST API depends on xref:identity:rest-api-authorization.adoc[REST API authorization] settings.
 
-image::images/rest_api_architecture_overview.png[diagram of architecture of a REST client integrated with Bonita]
+image::rest_api_architecture_overview.png[diagram of architecture of a REST client integrated with Bonita]
 
 === Execute REST calls and integrate the results in your application