davsclaus commented on code in PR #1139:
URL: https://github.com/apache/camel-website/pull/1139#discussion_r1488434661


##########
content/blog/2024/02/camel44-whatsnew/index.md:
##########
@@ -0,0 +1,169 @@
+---
+title: "Apache Camel 4.4 What's New"
+date: 2024-02-19
+authors: [davsclaus]
+categories: ["Releases"]
+preview: Details of what we have done in the Camel 4.4 release.
+---
+
+Apache Camel 4.4 (LTS) has just been [released](/blog/2024/02/RELEASE-4.4.0/).
+
+This release introduces a set of new features and noticeable improvements that 
we will cover in this blog post.
+
+## Camel Core
+
+The simple language has been improved with `hash` function, and further 
improved the embedded functions for `jsonpath`, `jq` and `xpath`
+making it easier to grab data from JSon or XML within your simple expression 
or predicates.
+
+We have optimized data formats to avoid converting payload to `byte[]` when 
unmarshalling, but allowing each data format
+to unmarshal the payload _as-is_. 
+
+Added JMX operation to update routes at runtime via XML format (requires 
turning on this feature). This can be
+useful for tooling where you can then change routes during troubleshooting an 
existing running Camel integration.
+
+## DSL
+
+TODO: Throttler EIP
+
+### Variables
+
+The biggest new feature in Camel 4.4 is the introduction of 
[variables](/manual/variables.adoc).
+
+A variable is a key/value that can hold a value that can either be private per 
`Exchange`, or shared per route, or globally.
+
+With variables, you can now more easily share data between routes and/or 
globally. Variables is also readily accessible

Review Comment:
   Not here in the blog - but on the actual doc of the feature itself - the 
blog is just high level



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to