Skip to content

Commit

Permalink
docs(content/update): Add Weld Issue Workaround Note
Browse files Browse the repository at this point in the history
Co-authored-by: Petros Savvidis <[email protected]>
Co-authored-by: Daniel Kelemen <[email protected]>

Related-to: camunda/camunda-bpm-platform#4434
  • Loading branch information
psavidis authored Jul 29, 2024
1 parent 29f714f commit 8fa8eeb
Showing 1 changed file with 7 additions and 0 deletions.
7 changes: 7 additions & 0 deletions content/update/patch-level.md
Original file line number Diff line number Diff line change
Expand Up @@ -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" >}}

**<h4>Jakarta Namespace</h4>**

`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" >}})

**<h4>Weld Class Loading Issues</h4>**
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 >}}

#### Migrate process applications
Expand Down

0 comments on commit 8fa8eeb

Please sign in to comment.