This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch rt
in repository https://gitbox.apache.org/repos/asf/camel.git
commit 3f6eeb5f497eb7c8faee5552e9091de056e46d51
Author: Claus Ibsen <claus.ib...@gmail.com>
AuthorDate: Wed Nov 27 09:15:43 2024 +0100
CAMEL-21475: camel-yaml-dsl - Using route templates with hardcoded ids
problem
---
.../modules/ROOT/pages/camel-4x-upgrade-guide-4_8.adoc | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git
a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_8.adoc
b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_8.adoc
index 51deb3016ee..4951161f31d 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_8.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_8.adoc
@@ -6,6 +6,14 @@ from both 4.0 to 4.1 and 4.1 to 4.2.
== Upgrading from 4.8.1 to 4.8.2
+=== camel-management
+
+==== Using Route Templates
+
+Camel will now ensure the created routes via route templates
+always use unique _nodePrefixId_ to ensure there are no duplicate id clashes,
when the template
+is used for creating multiple routes.
+
=== camel-debezium
To avoid split package that can be a problem in environments like OSGI, each
camel-debezium module has its own
