From cf604671f55d21b58466948d52fabb97bf46aa58 Mon Sep 17 00:00:00 2001 From: Braun Date: Fri, 23 Feb 2024 14:28:30 +0100 Subject: [PATCH] index pages --- java/architecture.md | 4 ++-- java/developing-applications/index.md | 16 ++++++++++++++++ java/operating-applications/index.md | 16 ++++++++++++++++ java/working-with-cql/query-api.md | 2 +- 4 files changed, 35 insertions(+), 3 deletions(-) create mode 100644 java/developing-applications/index.md create mode 100644 java/operating-applications/index.md diff --git a/java/architecture.md b/java/architecture.md index ecbdbb978..58b687935 100644 --- a/java/architecture.md +++ b/java/architecture.md @@ -34,7 +34,7 @@ Alternatively, you can even configure test on integration level to be executed l The following diagram illustrates the modular stack architecture and highlights the generic components: -The graphic is explained in the accompanying text. +The graphic is explained in the accompanying text. You can recognize five different areas of the stack, which comprise components according to different tasks: @@ -249,6 +249,6 @@ An example of a CAP application with OData V4 on Cloud Foundry environment: ### Custom Modules { #custom-modules } The plugin technique for the [standard modules](#standard-modules) can be used for custom modules in the same way. -By adding an additional dependency in the application project to the custom Maven module, the loaded module automatically adds functionality (usually handlers or providers) or extensions to the CDS model. +By adding an additional dependency in the application project to the custom Maven module, the loaded module automatically adds functionality (usually handlers or providers) or extensions to the CDS model. [Learn more about the CAP Java plugin technique.](../java/plugins){ .learn-more} diff --git a/java/developing-applications/index.md b/java/developing-applications/index.md new file mode 100644 index 000000000..90e7ffbf9 --- /dev/null +++ b/java/developing-applications/index.md @@ -0,0 +1,16 @@ +--- +synopsis: > + Learn here about developing a CAP Java application. + +status: released +--- + +# Developing CAP Java Applications + +{{ $frontmatter.synopsis }} + + + + diff --git a/java/operating-applications/index.md b/java/operating-applications/index.md new file mode 100644 index 000000000..10bb848e1 --- /dev/null +++ b/java/operating-applications/index.md @@ -0,0 +1,16 @@ +--- +synopsis: > + Learn here about operating a CAP Java application. + +status: released +--- + +# Operating CAP Java Applications + +{{ $frontmatter.synopsis }} + + + + diff --git a/java/working-with-cql/query-api.md b/java/working-with-cql/query-api.md index f890fe694..6ace6d6d8 100644 --- a/java/working-with-cql/query-api.md +++ b/java/working-with-cql/query-api.md @@ -759,7 +759,7 @@ Select.from("bookshop.Books").byId(1).lock(SHARED); ``` Not every entity exposed via a CDS entity can be locked with the `lock()` clause. To use the `lock()` clause, databases require that the target of such statements is represented by one of the following: -- a single table +- a single table - a simple view, so that the database can unambiguously identify which rows to lock Views that use joins, aggregate data, include calculated or coalesced fields cannot be locked. Some databases might have additional restrictions or limitations specific to them.