Skip to content

Commit 48b68ba

Browse files
authored
Merge branch 'master' into 4467-remove-swagger-from-docs
2 parents c2ad9b5 + 67e2e3c commit 48b68ba

File tree

3 files changed

+33
-5
lines changed

3 files changed

+33
-5
lines changed

content/installation/full/tomcat/manual.md

+15
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,21 @@ Throughout this guide we will use a number of variables to denote common path na
2525

2626
{{< /note >}}
2727

28+
{{< note title="Known Limitations in Tomcat 10" class="info" >}}
29+
30+
**<h4>Weld Class Loading Issues</h4>**
31+
32+
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's `/WEB-INF/lib` folder.
33+
To resolve this, move the weld library away from the war and place it into the `$CATALINA_HOME/lib` folder.
34+
35+
The above workaround is not guaranteed to work for cases with bean references between WAR deployments (WAR A referencing a bean from WAR B).
36+
37+
The following test scenarios fail on Tomcat 10:
38+
39+
* [CallActivityContextSwitchTest](https://github.com/camunda/camunda-bpm-platform/blob/f37877b822dabcbf3cee5806bd5833d18cdcb543/qa/integration-tests-engine/src/test/java/org/camunda/bpm/integrationtest/functional/context/CallActivityContextSwitchTest.java)
40+
* [CdiBeanCallActivityResolutionTest](https://github.com/camunda/camunda-bpm-platform/blob/f37877b822dabcbf3cee5806bd5833d18cdcb543/qa/integration-tests-engine/src/test/java/org/camunda/bpm/integrationtest/functional/cdi/CdiBeanCallActivityResolutionTest.java)
41+
{{< /note >}}
42+
2843

2944
# Setup
3045

content/update/minor/721-to-722/_index.md

+9-3
Original file line numberDiff line numberDiff line change
@@ -157,8 +157,15 @@ If your application uses a Docker image based on `Tomcat 9`, you need to perform
157157

158158
### Weld Class Loading Issues
159159

160-
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.
161-
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.
160+
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's `/WEB-INF/lib` folder.
161+
To resolve this, move the weld library away from the war and place it into the `$CATALINA_HOME/lib` folder.
162+
163+
The above workaround is not guaranteed to work for cases with bean references between WAR deployments (WAR A referencing a bean from WAR B).
164+
165+
The following test scenarios fail on Tomcat 10:
166+
167+
* [CallActivityContextSwitchTest](https://github.com/camunda/camunda-bpm-platform/blob/f37877b822dabcbf3cee5806bd5833d18cdcb543/qa/integration-tests-engine/src/test/java/org/camunda/bpm/integrationtest/functional/context/CallActivityContextSwitchTest.java)
168+
* [CdiBeanCallActivityResolutionTest](https://github.com/camunda/camunda-bpm-platform/blob/f37877b822dabcbf3cee5806bd5833d18cdcb543/qa/integration-tests-engine/src/test/java/org/camunda/bpm/integrationtest/functional/cdi/CdiBeanCallActivityResolutionTest.java)
162169

163170
# Camunda Run and Swagger Update
164171

@@ -167,5 +174,4 @@ To reduce the maintenance effort, Swagger is discontinued from `camunda-run`.
167174
From now on, the parameterisation of camunda-run scripts will not include the `--swaggerui` argument.
168175
Instead, you can always use [open-api][open-api] in conjunction with a `REST` client of your choice such as POSTMAN to achieve similar results.
169176

170-
171177
[open-api]: {{< ref "/reference/rest/openapi/_index.md" >}}

content/update/patch-level.md

+9-2
Original file line numberDiff line numberDiff line change
@@ -504,8 +504,15 @@ The `javax` modules won't work with `Tomcat 10`.
504504
For detailed steps of manual installation, follow the [Tomcat Manual Installation Guide]({{< ref "/installation/full/tomcat/manual.md" >}})
505505

506506
**<h4>Weld Class Loading Issues</h4>**
507-
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.
508-
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.
507+
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's `/WEB-INF/lib` folder.
508+
To resolve this, move the weld library away from the war and place it into the `$CATALINA_HOME/lib` folder.
509+
510+
The above workaround is not guaranteed to work for cases with bean references between WAR deployments (WAR A referencing a bean from WAR B).
511+
512+
The following test scenarios fail on Tomcat 10:
513+
514+
* [CallActivityContextSwitchTest](https://github.com/camunda/camunda-bpm-platform/blob/f37877b822dabcbf3cee5806bd5833d18cdcb543/qa/integration-tests-engine/src/test/java/org/camunda/bpm/integrationtest/functional/context/CallActivityContextSwitchTest.java)
515+
* [CdiBeanCallActivityResolutionTest](https://github.com/camunda/camunda-bpm-platform/blob/f37877b822dabcbf3cee5806bd5833d18cdcb543/qa/integration-tests-engine/src/test/java/org/camunda/bpm/integrationtest/functional/cdi/CdiBeanCallActivityResolutionTest.java)
509516
{{< /note >}}
510517

511518
# Full Distribution

0 commit comments

Comments
 (0)