This is an automated email from the ASF dual-hosted git repository.

davsclaus pushed a commit to branch jp
in repository https://gitbox.apache.org/repos/asf/camel.git

commit 8c35e1213036ec123377e8f092dc4e0afc047ca3
Author: Claus Ibsen <claus.ib...@gmail.com>
AuthorDate: Sun Nov 26 11:53:33 2023 +0100

    camel-jbang - Prototype for transform message command.
---
 .../ROOT/pages/camel-4x-upgrade-guide-4_3.adoc     | 22 +++++++++++++++-------
 1 file changed, 15 insertions(+), 7 deletions(-)

diff --git 
a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_3.adoc 
b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_3.adoc
index f97b3b25b7c..08f19a47b7d 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_3.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_3.adoc
@@ -6,6 +6,21 @@ from both 4.0 to 4.1 and 4.1 to 4.2.
 
 == Upgrading Camel 4.2 to 4.3
 
+=== Throttle EIP
+
+Throttle now uses the number of concurrent requests as the throttling measure 
instead of the number of requests
+per period.
+
+The `throttle` parameter now specifies the maximum number of concurrent 
requests,
+and there is no longer support for the `timePeriodMillis` option.
+
+=== camel-jbang
+
+The `camel transform` command has been renamed to `camel transform route` as 
this command is used for transforming
+routes between DSLs such as XML to YAML.
+
+There is a new `camel transform message` command to do message transformation.
+
 === camel-kafka
 
 The behavior for `breakOnFirstError` was altered as numerous issues were 
fixed. The behavior related to committing 
@@ -20,10 +35,3 @@ the behavior described in the documentation.
 When using the `AsyncCommitManager` then the offset will be committed so that 
the payload is continually retried. This was
 the behavior described in the documentation.
 
-=== throttle
-
-Throttle now uses the number of concurrent requests as the throttling measure 
instead of the number of requests
-per period.
-
-The `throttle` parameter now specifies the maximum number of concurrent 
requests,
-and there is no longer support for the `timePeriodMillis` option.

Reply via email to