This is an automated email from the ASF dual-hosted git repository.
gnodet pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/main by this push:
new 239475b81ff7 chore: fix state-store adoc duplicate include and
incomplete operation list
239475b81ff7 is described below
commit 239475b81ff77e3b565125b2109c73dc21affd72
Author: Guillaume Nodet <[email protected]>
AuthorDate: Tue Aug 25 20:38:57 2026 +0200
chore: fix state-store adoc duplicate include and incomplete operation list
- Remove duplicate include of component-configure-options.adoc (was in both
component-configure options and component options sections)
- Update operation list to include all 8 operations: put, putIfAbsent, get,
delete, contains, keys, size, clear
- Regenerate catalog copy to match source changes
Co-Authored-By: Claude Opus 4.6 <[email protected]>
---
.../resources/org/apache/camel/catalog/docs/state-store-component.adoc | 3 +--
.../camel-state-store/src/main/docs/state-store-component.adoc | 3 +--
2 files changed, 2 insertions(+), 4 deletions(-)
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/state-store-component.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/state-store-component.adoc
index 8d2537e9df3d..c37fb9acaf18 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/state-store-component.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/state-store-component.adoc
@@ -32,7 +32,7 @@ Use State Store when:
* You need a *simple key-value API* and want to switch backends without
changing route logic.
* You are *migrating from MuleSoft* and want an Object Store equivalent.
* You want *backend portability* — develop with in-memory, deploy with Redis
or Infinispan.
-* Your use case is limited to *put, get, delete, contains, keys* operations.
+* Your use case is limited to *put, putIfAbsent, get, delete, contains, keys,
size, clear* operations.
[width="100%",cols="1,2,1",options="header"]
|===
@@ -53,7 +53,6 @@ Where `storeName` is a logical name for the store. Endpoints
with the same `stor
share the same backend instance within the same `CamelContext`.
// component-configure options: START
-include::partial$component-configure-options.adoc[]
// component-configure options: END
// component options: START
diff --git
a/components/camel-state-store/camel-state-store/src/main/docs/state-store-component.adoc
b/components/camel-state-store/camel-state-store/src/main/docs/state-store-component.adoc
index 8d2537e9df3d..c37fb9acaf18 100644
---
a/components/camel-state-store/camel-state-store/src/main/docs/state-store-component.adoc
+++
b/components/camel-state-store/camel-state-store/src/main/docs/state-store-component.adoc
@@ -32,7 +32,7 @@ Use State Store when:
* You need a *simple key-value API* and want to switch backends without
changing route logic.
* You are *migrating from MuleSoft* and want an Object Store equivalent.
* You want *backend portability* — develop with in-memory, deploy with Redis
or Infinispan.
-* Your use case is limited to *put, get, delete, contains, keys* operations.
+* Your use case is limited to *put, putIfAbsent, get, delete, contains, keys,
size, clear* operations.
[width="100%",cols="1,2,1",options="header"]
|===
@@ -53,7 +53,6 @@ Where `storeName` is a logical name for the store. Endpoints
with the same `stor
share the same backend instance within the same `CamelContext`.
// component-configure options: START
-include::partial$component-configure-options.adoc[]
// component-configure options: END
// component options: START
