From 4379ac2ee61162dbdd3f5b74de1ddcf5f7ff2c04 Mon Sep 17 00:00:00 2001 From: Petros Savvidis Date: Wed, 24 Jul 2024 11:50:33 +0300 Subject: [PATCH 1/4] Add note to migration guide --- content/update/minor/721-to-722/_index.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/content/update/minor/721-to-722/_index.md b/content/update/minor/721-to-722/_index.md index 4c2b0dcc91..8ee39c7a51 100644 --- a/content/update/minor/721-to-722/_index.md +++ b/content/update/minor/721-to-722/_index.md @@ -152,4 +152,9 @@ Replace the artifact `camunda-engine-rest-$PLATFORM_VERSION-tomcat.war` with `ca ### Migrating to the Tomcat 10 Docker Image -If your application uses a Docker image based on `Tomcat 9`, you need to perform the above migration steps yourself before your application is compatible with the `jakarta` namespace changes the new Tomcat version introduces. \ No newline at end of file +If your application uses a Docker image based on `Tomcat 9`, you need to perform the above migration steps yourself before your application is compatible with the `jakarta` namespace changes the new Tomcat version introduces. + +### CDI and Weld issues + +In deployment scenarios involving one or more process applications with managed beans, classloading issues may occur if the WELD library is directly embedded in the WAR or process application deployment. +To resolve this, it is recommended to relocate the WELD library from the WAR or process application deployment to the Tomcat server's library folder. From 33bc1a00d7182af627bd357d752f5a143c1598cc Mon Sep 17 00:00:00 2001 From: Petros Savvidis Date: Wed, 24 Jul 2024 11:50:41 +0300 Subject: [PATCH 2/4] Add note to migration patch-level section --- content/update/patch-level.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/content/update/patch-level.md b/content/update/patch-level.md index ee03eb0f65..e338a4410a 100644 --- a/content/update/patch-level.md +++ b/content/update/patch-level.md @@ -493,12 +493,19 @@ This API is an internal API, which means it's **not** part of the public [REST A This version supports all the necessary building-block modules for our users to use `camunda-bpm-platform` community and enterprise editions in conjunction with `Tomcat 10.1`. {{< note title="Heads-up!" class="warning" >}} + +**

Jakarta Namespace

** + `Tomcat 10` is compatible with the `jakarta` namespace. If you wish to use it, the `jakarta` modules needs to be used (`camunda-webapp-tomcat-jakarta`, `camunda-engine-rest-jakarta`). The `javax` modules won't work with `Tomcat 10`. For detailed steps of manual installation, follow the [Tomcat Manual Installation Guide]({{< ref "/installation/full/tomcat/manual.md" >}}) + +**

Weld Classloading Issues

** +In deployment scenarios involving one or more process applications with managed beans, classloading issues may occur if the WELD library is directly embedded in the WAR or process application deployment. +To resolve this, it is recommended to relocate the WELD library from the WAR or process application deployment to the Tomcat server's library folder. {{< /note >}} # Full Distribution From cf7339ac160702ccbc6d158733f7371c4a94a75d Mon Sep 17 00:00:00 2001 From: psavidis <69160690+psavidis@users.noreply.github.com> Date: Fri, 26 Jul 2024 12:53:45 +0300 Subject: [PATCH 3/4] Update content/update/patch-level.md Co-authored-by: Daniel Kelemen --- content/update/patch-level.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/update/patch-level.md b/content/update/patch-level.md index e338a4410a..94dc66fa37 100644 --- a/content/update/patch-level.md +++ b/content/update/patch-level.md @@ -503,7 +503,7 @@ The `javax` modules won't work with `Tomcat 10`. For detailed steps of manual installation, follow the [Tomcat Manual Installation Guide]({{< ref "/installation/full/tomcat/manual.md" >}}) -**

Weld Classloading Issues

** +**

Weld Class Loading Issues

** In deployment scenarios involving one or more process applications with managed beans, classloading issues may occur if the WELD library is directly embedded in the WAR or process application deployment. To resolve this, it is recommended to relocate the WELD library from the WAR or process application deployment to the Tomcat server's library folder. {{< /note >}} From ae3bfddb7174d17f647a6ffef10a5983b34acc89 Mon Sep 17 00:00:00 2001 From: Petros Savvidis Date: Fri, 26 Jul 2024 12:55:21 +0300 Subject: [PATCH 4/4] Change Patch Title --- content/update/minor/721-to-722/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/update/minor/721-to-722/_index.md b/content/update/minor/721-to-722/_index.md index 8ee39c7a51..13c2595f60 100644 --- a/content/update/minor/721-to-722/_index.md +++ b/content/update/minor/721-to-722/_index.md @@ -154,7 +154,7 @@ Replace the artifact `camunda-engine-rest-$PLATFORM_VERSION-tomcat.war` with `ca If your application uses a Docker image based on `Tomcat 9`, you need to perform the above migration steps yourself before your application is compatible with the `jakarta` namespace changes the new Tomcat version introduces. -### CDI and Weld issues +### Weld Class Loading Issues In deployment scenarios involving one or more process applications with managed beans, classloading issues may occur if the WELD library is directly embedded in the WAR or process application deployment. To resolve this, it is recommended to relocate the WELD library from the WAR or process application deployment to the Tomcat server's library folder.