Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs(content/update): Add Weld Issue Workaround Note #1664

Merged
merged 4 commits into from
Jul 26, 2024
Merged

docs(content/update): Add Weld Issue Workaround Note #1664

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
4379ac2
Add note to migration guide
psavidis Jul 24, 2024
33bc1a0
Add note to migration patch-level section
psavidis Jul 24, 2024
cf7339a
Update content/update/patch-level.md
psavidis Jul 26, 2024
ae3bfdd
Change Patch Title
psavidis Jul 26, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion content/update/minor/721-to-722/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
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
psavidis marked this conversation as resolved.
Show resolved Hide resolved

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.
7 changes: 7 additions & 0 deletions content/update/patch-level.md
View file
Open in desktop
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 Classloading Issues</h4>**
psavidis marked this conversation as resolved.
Show resolved Hide resolved
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.
psavidis marked this conversation as resolved.
Show resolved Hide resolved
{{< /note >}}

# Full Distribution
Expand Down