This is an automated email from the ASF dual-hosted git repository.
rzo1 pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/tomee.git
The following commit(s) were added to refs/heads/main by this push:
new 096f05c879 Updates doc links towards Tomcat doc to 11.0 pendant (#2513)
096f05c879 is described below
commit 096f05c879c6d7ecadabf0e5416c2d8c09e0aa13
Author: Martin Wiesner <[email protected]>
AuthorDate: Sun Feb 22 21:01:07 2026 +0100
Updates doc links towards Tomcat doc to 11.0 pendant (#2513)
---
docs/admin/cluster/index.adoc | 2 +-
docs/admin/configuration/resources.adoc | 2 +-
docs/datasource-configuration-by-creator.adoc | 3 +--
docs/ejb-over-ssl.adoc | 6 +++---
docs/refcard/refcard.html | 2 +-
docs/tomee-cluster.txt | 2 +-
6 files changed, 8 insertions(+), 9 deletions(-)
diff --git a/docs/admin/cluster/index.adoc b/docs/admin/cluster/index.adoc
index c2927f8628..dc10c72ed0 100644
--- a/docs/admin/cluster/index.adoc
+++ b/docs/admin/cluster/index.adoc
@@ -5,7 +5,7 @@
== Session clustering
-TomEE fully relies on Tomcat clustering:
https://tomcat.apache.org/tomcat-7.0-doc/cluster-howto.html[Tomcat Clustering].
+TomEE fully relies on Tomcat clustering:
https://tomcat.apache.org/tomcat-11.0-doc/cluster-howto.html[Tomcat Clustering].
The configuration is mainly in `conf/server.xml` and since TomEE 7 CDI
`@SessionScoped` is transparently clustered
through the session.
diff --git a/docs/admin/configuration/resources.adoc
b/docs/admin/configuration/resources.adoc
index c4ba60b2ee..c47e168b27 100644
--- a/docs/admin/configuration/resources.adoc
+++ b/docs/admin/configuration/resources.adoc
@@ -95,7 +95,7 @@ configure it here are the common properties:
You can set the boolean `JtaManaged` to false if you don't want your
datasource to be using JTA - if you manage transactions yourself.
-Then other configurations are linked the pool the datasource is using. By
default TomEE uses
https://tomcat.apache.org/tomcat-7.0-doc/jdbc-pool.html[tomcat-jdbc] but we
also provide
+Then other configurations are linked the pool the datasource is using. By
default TomEE uses
https://tomcat.apache.org/tomcat-11.0-doc/jdbc-pool.html[tomcat-jdbc] but we
also provide
https://commons.apache.org/proper/commons-dbcp/configuration.html[commons-dbcp]
(2 for TomEE 7.x and 1 for TomEE 1.x).
The properties are then the related configurations with these particular
entries we try to keep in sync for both:
diff --git a/docs/datasource-configuration-by-creator.adoc
b/docs/datasource-configuration-by-creator.adoc
index 9cd1577e84..edc994cca6 100644
--- a/docs/datasource-configuration-by-creator.adoc
+++ b/docs/datasource-configuration-by-creator.adoc
@@ -60,8 +60,7 @@ the latest version of DBCP but TomEE 1.7.x is not using this
version).
== Tomcat JDBC
-Note: details are at
-https://tomcat.apache.org/tomcat-7.0-doc/jdbc-pool.html
+Note: details are at https://tomcat.apache.org/tomcat-11.0-doc/jdbc-pool.html
* AbandonWhenPercentageFull
* AccessToUnderlyingConnectionAllowed
diff --git a/docs/ejb-over-ssl.adoc b/docs/ejb-over-ssl.adoc
index aeea493cdb..c59e79f707 100644
--- a/docs/ejb-over-ssl.adoc
+++ b/docs/ejb-over-ssl.adoc
@@ -17,7 +17,7 @@ Note, TomEE can be setup to support *ejbds*.
First, you'll need to setup Tomcat (TomEE) with SSL as described here:
-http://tomcat.apache.org/tomcat-7.0-doc/ssl-howto.html
+http://tomcat.apache.org/tomcat-11.0-doc/ssl-howto.html
Once that is done and the `tomee` webapp can be accessed with `https`,
an EJB client can invoke over `https` using the following
@@ -43,9 +43,9 @@ like connection reset, you'll have to set 'https.protocols'
system
property. 'https.protocols' property must be set according to the
SSLProtocol parameter of the HTTPS connector configuration :
-http://tomcat.apache.org/tomcat-7.0-doc/config/http.html
+http://tomcat.apache.org/tomcat-11.0-doc/config/http.html
-You can also have a look a this :
+You can also have a look at this :
http://docs.oracle.com/javase/1.4.2/docs/guide/plugin/developer_guide/faq/troubleshooting.html
diff --git a/docs/refcard/refcard.html b/docs/refcard/refcard.html
index 295e755d57..574b5574b1 100644
--- a/docs/refcard/refcard.html
+++ b/docs/refcard/refcard.html
@@ -366,7 +366,7 @@ OpenEJB.handlers = 5tomee.org.apache.juli.FileHandler,\
java.util.logging.ConsoleHandler
# more on tomcat website:
-# http://tomcat.apache.org/tomcat-7.0-doc/logging.html</code></pre>
+# http://tomcat.apache.org/tomcat-11.0-doc/logging.html</code></pre>
</div>
</div>
</div></td>
diff --git a/docs/tomee-cluster.txt b/docs/tomee-cluster.txt
index e74c37d152..45c2f37d4c 100644
--- a/docs/tomee-cluster.txt
+++ b/docs/tomee-cluster.txt
@@ -3,7 +3,7 @@ The scope of this document to to define how Apache TomEE can be
configured for H
The configuration will focus on two local instances, with a view to an open
ended remote configuration.
It is beyond the scope of this documentation to discuss Tomcat CLustering in
depth.
-Please read the [Apache Tomcat Clustering
Howto](http://tomcat.apache.org/tomcat-7.0-doc/cluster-howto.html) for more
information.
+Please read the [Apache Tomcat Clustering
Howto](http://tomcat.apache.org/tomcat-11.0-doc/cluster-howto.html) for more
information.
###Local cluster
To test clustering locally (on the same physical machine) the default ports
need to be modified on the second TomEE server.
