This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch new440
in repository https://gitbox.apache.org/repos/asf/camel-website.git
The following commit(s) were added to refs/heads/new440 by this push:
new 9278c0e9 Camel 4.4 whats new. WIP
9278c0e9 is described below
commit 9278c0e958a30d712b7bc2437c583ed3dd20976a
Author: Claus Ibsen <[email protected]>
AuthorDate: Tue Feb 13 14:15:08 2024 +0100
Camel 4.4 whats new. WIP
---
content/blog/2024/02/camel44-whatsnew/index.md | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/content/blog/2024/02/camel44-whatsnew/index.md
b/content/blog/2024/02/camel44-whatsnew/index.md
index a9b1e4ae..8b900ccd 100644
--- a/content/blog/2024/02/camel44-whatsnew/index.md
+++ b/content/blog/2024/02/camel44-whatsnew/index.md
@@ -81,6 +81,11 @@ The source (input) is from another variable named `beer2`.
You can also specify
if you remove `source` then the message body is used as input (default).
The result is converted to a Java `float`,
+**NOTE:**
+If you take a closer look in the screenshot above, then the debugger reveals
that the `Exchange` has no message headers,
+and that the message body is empty (`null`). The example is exclusively using
variables to gather and compute data; without
+the need to store and restore data on message header/body during routing. This
is a cleaner and elegant practice.
+
## Camel JBang (Camel CLI)
