chore(content/update): Refactor and Amend Weld Message

* Refactor the weld message to make it more clear
* Add workaround limitations for cases that involve cross-archive bean references

Co-authored-by: petros.savvidis
Co-authored-by: tasso94

Related-to: camunda/camunda-bpm-platform#4499

Author: psavidis

content/installation/full/tomcat/manual.md

@@ -25,6 +25,21 @@ Throughout this guide we will use a number of variables to denote common path na
 
 {{< /note >}}
 
+{{< note title="Known Limitations in Tomcat 10" class="info" >}}
+
+**<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's `/WEB-INF/lib` folder.
+To resolve this, move the weld library away from the war and place it into the `$CATALINA_HOME/lib` folder.
+
+The above workaround is not guaranteed to work for cases with bean references between WAR deployments (WAR A referencing a bean from WAR B).
+
+The following test scenarios fail on Tomcat 10:
+
+* [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)
+* [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)
+{{< /note >}}
+
 
 # Setup
 

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

@@ -156,5 +156,12 @@ If your application uses a Docker image based on `Tomcat 9`, you need to perform
 
 ### 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.
+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.
+To resolve this, move the weld library away from the war and place it into the `$CATALINA_HOME/lib` folder.
+
+The above workaround is not guaranteed to work for cases with bean references between WAR deployments (WAR A referencing a bean from WAR B).
+
+The following test scenarios fail on Tomcat 10:
+
+* [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)
+* [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)

content/update/patch-level.md

@@ -504,8 +504,15 @@ 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.
+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.
+To resolve this, move the weld library away from the war and place it into the `$CATALINA_HOME/lib` folder.
+
+The above workaround is not guaranteed to work for cases with bean references between WAR deployments (WAR A referencing a bean from WAR B). 
+
+The following test scenarios fail on Tomcat 10:
+
+* [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)
+* [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)
 {{< /note >}}
 
 # Full Distribution