Tomcat 10.x
This page has been automatically generated by Cargo's build. Do not edit it directly as it'll be overwritten next time it's generated again.
Users of Tomcat 10.x onwards should be aware that, as a result of the move from Java EE to Jakarta EE as part of the transfer of Java EE to the Eclipse Foundation, the primary package for all implemented APIs has changed from javax.*
to jakarta.*
. This will almost certainly require code changes to enable applications to migrate to Tomcat 10.x and later.
Container Features
Feature name |
Java API |
Ant tasks |
Maven 3 plugin |
Comment |
---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Running multiple Tomcat 7.x / Tomcat 8.x / Tomcat 9.x / Tomcat 10.x embedded containers within the same JVM
Tomcat 7.x has introduced a class called TomcatURLStreamHandlerFactory
where the singleton has a static instance
field and a final registered
attribute which are not always in sync and cause unexpected exceptions. Due to this, it is not possible to execute Tomcat 7.x, Tomcat 8.x, Tomcat 9.x and Tomcat 10.x embedded in the same JVM, in addition running one of these Tomcat embedded versions one after the other within the same JVM but different classpaths might also fail.
If you want to be safe, prefer using the Installed Container. Also note that Tomcat 11.x onwards has gotten rid of that class.
Configuration Features
Feature name |
Java API |
Ant tasks |
Maven 3 plugin |
Comment |
---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Deployer Features
Feature name |
Java API |
Ant tasks |
Maven 3 plugin |
Comment |
---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Other Features
Feature name |
Java API |
Ant tasks |
Maven 3 plugin |
Comment |
---|---|---|---|---|
|
|
|
|
Supported Configuration properties
The tables below list both the general configuration properties as well as the container-specific ones.
Standalone Local Configuration Properties
For installed container o.c.c.c.tomcat.Tomcat10xInstalledLocalContainer
Property name |
Java Property |
Supported? |
Default value |
Javadoc |
---|---|---|---|---|
|
|
|||
|
JAVA_HOME version 8 (Tomcat 10.0.x) or 11 (Tomcat 10.1.x onwards) or newer |
|||
|
N/A |
|||
|
|
|||
|
|
|||
|
|
|||
|
|
|||
|
|
|||
|
N/A |
|||
|
|
|||
|
|
|||
|
N/A |
|||
|
N/A |
|||
|
|
|||
|
N/A |
|||
|
N/A |
|||
|
N/A |
|||
|
N/A |
|||
|
N/A |
|||
|
N/A |
|||
|
N/A |
|||
|
N/A |
|||
|
N/A |
|||
|
N/A |
|||
|
N/A |
|||
|
N/A |
|||
|
N/A |
|||
|
|
|||
|
|
|||
|
|
|||
|
|
|||
|
N/A |
|||
|
|
|||
|
|
|||
|
N/A |
|||
|
N/A |
|||
|
|
Datasource and Resource configuration
In addition to the forementioned properties, this container configuration can also set up datasources and/or resources.
For more details, please read: DataSource and Resource Support.
Configuring HTTP/2 for Tomcat 8.5 and above
Tomcat 8.5 and above support HTTP/2.
For further information on how to enable this, please refer to Configuring HTTP/2 for Tomcat 8.5 and above.
For embedded container o.c.c.c.tomcat.Tomcat10xEmbeddedLocalContainer
Property name |
Java Property |
Supported? |
Default value |
Javadoc |
---|---|---|---|---|
|
|
|||
|
JAVA_HOME version 8 (Tomcat 10.0.x) or 11 (Tomcat 10.1.x onwards) or newer |
|||
|
N/A |
|||
|
|
|||
|
|
|||
|
|
|||
|
|
|||
|
N/A |
|||
|
|
|||
|
|
|||
|
N/A |
|||
|
N/A |
|||
|
|
|||
|
N/A |
|||
|
N/A |
|||
|
N/A |
|||
|
N/A |
|||
|
N/A |
|||
|
N/A |
|||
|
N/A |
|||
|
N/A |
|||
|
N/A |
|||
|
N/A |
|||
|
N/A |
|||
|
N/A |
|||
|
N/A |
|||
|
|
|||
|
|
|||
|
|
|||
|
|
|||
|
|
|||
|
N/A |
|||
|
|
|||
|
|
|||
|
N/A |
|||
|
N/A |
|||
|
|
Datasource and Resource configuration
In addition to the forementioned properties, this container configuration can also set up datasources and/or resources.
For more details, please read: DataSource and Resource Support.
Configuring HTTP/2 for Tomcat 8.5 and above
Tomcat 8.5 and above support HTTP/2.
For further information on how to enable this, please refer to Configuring HTTP/2 for Tomcat 8.5 and above.
Existing Local Configuration Properties
For installed container o.c.c.c.tomcat.Tomcat10xInstalledLocalContainer
Property name |
Java Property |
Supported? |
Default value |
Javadoc |
---|---|---|---|---|
|
|
|||
|
JAVA_HOME version 8 (Tomcat 10.0.x) or 11 (Tomcat 10.1.x onwards) or newer |
|||
|
N/A |
|||
|
|
|||
|
|
|||
|
|
|||
|
N/A |
|||
|
|
|||
|
N/A |
For embedded container o.c.c.c.tomcat.Tomcat10xEmbeddedLocalContainer
Property name |
Java Property |
Supported? |
Default value |
Javadoc |
---|---|---|---|---|
|
|
|||
|
JAVA_HOME version 8 (Tomcat 10.0.x) or 11 (Tomcat 10.1.x onwards) or newer |
|||
|
N/A |
|||
|
|
|||
|
|
|||
|
N/A |
|||
|
|
|||
|
N/A |
|||
|
|
Runtime Configuration Properties
For remote container o.c.c.c.tomcat.Tomcat10xRemoteContainer
Property name |
Java Property |
Supported? |
Default value |
Javadoc |
---|---|---|---|---|
|
|
|||
|
|
|||
|
N/A |
|||
|
|
|||
|
N/A |
|||
|
N/A |
|||
|
|
|||
|
|
|||
|
|
With Tomcat 10, the Tomcat manager has multiple aspects to be careful about:
- Your browser by default accesses the HTML-based manager whereas Codehaus Cargo needs to use the text-based manager. As a result, if you want to set the
RemotePropertySet.URI
manually, please make sure you set the URL for the text-based manager, for examplehttp://production27:8080/manager/text
- The text-based manager requires to be accessed by a user with the
manager-script
role; and by default no user has that role. As a result, please make sure you modify yourtomcat-users.xml
file to give that role to a user.
You can read more in the Tomcat documentation: https://tomcat.apache.org/tomcat-10.0-doc/manager-howto.html
Tested On
This container is automatically tested by the Continous Integration system every time there is a code change.
The server used for tests is downloaded from: https://repo.maven.apache.org/maven2/org/apache/tomcat/tomcat/10.1.23/tomcat-10.1.23.zip