From c95ab10083fd60969d13ff4d8bd86b02f2345251 Mon Sep 17 00:00:00 2001 From: I569192 Date: Fri, 13 Feb 2026 14:24:45 +0100 Subject: [PATCH 1/4] add fragments --- guides/protocols/_menu.md | 1 + guides/protocols/index.md | 2 ++ 2 files changed, 3 insertions(+) diff --git a/guides/protocols/_menu.md b/guides/protocols/_menu.md index 23c41d0954..a42be1ba5b 100644 --- a/guides/protocols/_menu.md +++ b/guides/protocols/_menu.md @@ -5,3 +5,4 @@ # [OpenAPI](openapi.md) # [AsyncAPI](asyncapi.md) # [InA Analytics](../../../guides/protocols/embedded-analytics) +
diff --git a/guides/protocols/index.md b/guides/protocols/index.md index e726c998b0..4708dba27b 100644 --- a/guides/protocols/index.md +++ b/guides/protocols/index.md @@ -8,6 +8,7 @@ CAP supports the following service protocols: - **OData**: A widely used protocol for building and consuming RESTful APIs. CAP provides built-in support for OData v2 and v4, allowing you to easily expose your data models as OData services. - **OpenAPI**: A specification for building APIs that allows you to define your API endpoints, request/response formats, and authentication methods. CAP can generate OpenAPI specifications for your services, enabling easy integration with other systems. - **AsyncAPI**: A specification for defining asynchronous APIs, such as those using messaging protocols. CAP supports AsyncAPI for building event-driven applications and integrating with messaging systems. +
## Using Protocols in CAP To use a specific protocol in your CAP application, you typically need to configure your service definitions and handlers accordingly. Here are some general steps to get started: @@ -24,6 +25,7 @@ For more detailed information on each protocol and how to implement them in CAP, - [OData APIs](odata.md) - [OpenAPI](openapi.md) - [AsyncAPI](asyncapi.md) +
These guides provide step-by-step instructions, examples, and best practices for working with each protocol in your CAP applications. From 1fc92c04ecac4d9009089a60af8045dc58b04000 Mon Sep 17 00:00:00 2001 From: I569192 Date: Mon, 16 Feb 2026 14:01:07 +0100 Subject: [PATCH 2/4] add one more fragment --- guides/protocols/protocol-adapters.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/guides/protocols/protocol-adapters.md b/guides/protocols/protocol-adapters.md index f9f0036c09..27f91c9fe8 100644 --- a/guides/protocols/protocol-adapters.md +++ b/guides/protocols/protocol-adapters.md @@ -29,4 +29,5 @@ In this example, the `cds.serve()` method is used to expose the `my-service` ser - [Core Data APIs](./core-data-apis.md) - [OData](./odata.md) - [OpenAPI](./openapi.md) -- [AsyncAPI](./asyncapi.md) \ No newline at end of file +- [AsyncAPI](./asyncapi.md) +
From 3e327b9719f8138b63bd278cfa9e8dc43ede7485 Mon Sep 17 00:00:00 2001 From: I569192 Date: Mon, 16 Feb 2026 16:10:28 +0100 Subject: [PATCH 3/4] update menu fragment --- guides/protocols/_menu.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guides/protocols/_menu.md b/guides/protocols/_menu.md index a42be1ba5b..26a26251b5 100644 --- a/guides/protocols/_menu.md +++ b/guides/protocols/_menu.md @@ -5,4 +5,4 @@ # [OpenAPI](openapi.md) # [AsyncAPI](asyncapi.md) # [InA Analytics](../../../guides/protocols/embedded-analytics) -
+# [MCP](../../../guides/protocols/mcp) From 51707fb3af2d5573a35b1a47d126e025a0ffc074 Mon Sep 17 00:00:00 2001 From: I569192 Date: Mon, 16 Feb 2026 16:20:00 +0100 Subject: [PATCH 4/4] update to internal from unreleased --- guides/protocols/_menu.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guides/protocols/_menu.md b/guides/protocols/_menu.md index 26a26251b5..f350763fa0 100644 --- a/guides/protocols/_menu.md +++ b/guides/protocols/_menu.md @@ -5,4 +5,4 @@ # [OpenAPI](openapi.md) # [AsyncAPI](asyncapi.md) # [InA Analytics](../../../guides/protocols/embedded-analytics) -# [MCP](../../../guides/protocols/mcp) +# [MCP](../../../guides/protocols/mcp)