You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: content/installation/full/tomcat/manual.md
+15
Original file line number
Diff line number
Diff line change
@@ -25,6 +25,21 @@ Throughout this guide we will use a number of variables to denote common path na
25
25
26
26
{{< /note >}}
27
27
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).
Copy file name to clipboardexpand all lines: content/update/minor/721-to-722/_index.md
+9-3
Original file line number
Diff line number
Diff line change
@@ -157,8 +157,15 @@ If your application uses a Docker image based on `Tomcat 9`, you need to perform
157
157
158
158
### Weld Class Loading Issues
159
159
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).
Copy file name to clipboardexpand all lines: content/update/patch-level.md
+9-2
Original file line number
Diff line number
Diff line change
@@ -504,8 +504,15 @@ The `javax` modules won't work with `Tomcat 10`.
504
504
For detailed steps of manual installation, follow the [Tomcat Manual Installation Guide]({{< ref "/installation/full/tomcat/manual.md" >}})
505
505
506
506
**<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).
0 commit comments