This is an automated email from the ASF dual-hosted git repository.
davsclaus 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 9288d167e087 CAMEL-16861: Update docs
9288d167e087 is described below
commit 9288d167e08750c7344e7a6a3b00c9590b52e907
Author: Claus Ibsen <[email protected]>
AuthorDate: Fri Feb 20 08:36:48 2026 +0100
CAMEL-16861: Update docs
---
docs/user-manual/modules/ROOT/pages/exchange-pattern.adoc | 2 +-
docs/user-manual/modules/ROOT/pages/exchange.adoc | 9 ++-------
docs/user-manual/modules/ROOT/pages/expression.adoc | 9 +++++----
3 files changed, 8 insertions(+), 12 deletions(-)
diff --git a/docs/user-manual/modules/ROOT/pages/exchange-pattern.adoc
b/docs/user-manual/modules/ROOT/pages/exchange-pattern.adoc
index 8cb1c8aa77da..a3e232504e98 100644
--- a/docs/user-manual/modules/ROOT/pages/exchange-pattern.adoc
+++ b/docs/user-manual/modules/ROOT/pages/exchange-pattern.adoc
@@ -9,7 +9,7 @@ Integration Patterns] they are:
* xref:components:eips:event-message.adoc[Event Message] (or one-way)
* xref:components:eips:requestReply-eip.adoc[Request Reply]
-In Camel we have an
+In Camel, we have an
`org.apache.camel.ExchangePattern`
enumeration which can be configured on the *exchangePattern* property on
the Message Exchange indicating if a message
diff --git a/docs/user-manual/modules/ROOT/pages/exchange.adoc
b/docs/user-manual/modules/ROOT/pages/exchange.adoc
index 1aef955811c6..7c829dbef276 100644
--- a/docs/user-manual/modules/ROOT/pages/exchange.adoc
+++ b/docs/user-manual/modules/ROOT/pages/exchange.adoc
@@ -11,10 +11,5 @@ Thanks to this, Apache Camel can support different
integration patterns such as:
== Learn More About Exchanges
* xref:manual::exchange-pooling.adoc[Exchange Pooling]
-* xref:manual::using-exchange-pattern-annotations.adoc[Using Exchange Pattern
Annotations]
-
-== Implementation Details
-
-There are concrete classes that implement the `Exchange` interface for each
Camel-supported communications technology. For example, the `JmsExchange` class
provides a JMS-specific implementation of the `Exchange` interface. The public
API of the `Exchange` interface is limited intentionally: we expect that each
class that implements this interface will provide its own technology-specific
operations.
-
-Application-level programmers rarely access the `Exchange` interface (or
classes that implement it) directly. However, many classes in Camel are generic
types that are instantiated on (a class that implements) `Exchange`. Because of
this, the `Exchange` interface appears a lot in the generic signatures of
classes and methods.
+* xref:manual::exchange-pattern.adoc[Message Exchange Pattern]
+* xref:manual::using-exchange-pattern-annotations.adoc[Using Message Exchange
Pattern Annotations]
diff --git a/docs/user-manual/modules/ROOT/pages/expression.adoc
b/docs/user-manual/modules/ROOT/pages/expression.adoc
index c5922b421ac8..265ff8063db0 100644
--- a/docs/user-manual/modules/ROOT/pages/expression.adoc
+++ b/docs/user-manual/modules/ROOT/pages/expression.adoc
@@ -2,7 +2,9 @@
Expressions and xref:predicate.adoc[Predicates] can then be used to
create the various
xref:components:eips:enterprise-integration-patterns.adoc[Enterprise
-Integration Patterns] in the xref:dsl.adoc[DSL] like with the
xref:components:eips:recipientList-eip.adoc[Recipient List] EIP.
+Integration Patterns] in the xref:dsl.adoc[DSL] like with the
+xref:components:eips:choice-eip.adoc[Content Based Router] EIP, or
+xref:components:eips:recipientList-eip.adoc[Recipient List] EIP.
To support dynamic rules Camel supports pluggable
https://www.javadoc.io/doc/org.apache.camel/camel-api/current/org/apache/camel/Expression.html[Expression]
@@ -21,9 +23,8 @@ class].
The API for a Camel Expression is defined in the
`org.apache.camel.Expression` interface as shown:
-
[source,java]
--------------------------------------------------------------------------------
+----
public interface Expression {
/**
@@ -35,5 +36,5 @@ public interface Expression {
*/
<T> T evaluate(Exchange exchange, Class<T> type);
}
--------------------------------------------------------------------------------
+----
