[
https://issues.apache.org/jira/browse/AXIS2-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17941695#comment-17941695
]
Jeff Thomas edited comment on AXIS2-6090 at 4/7/25 7:25 PM:
------------------------------------------------------------
For me it is not (currently) causing problems - we are heavily basing our
dependency levels on the Spring Boot (currently 3.4.4) dependencies which are
imported as BOM in parent POM - this nails our Tomcat Level at 10.1.* currently.
It is also only imported in the axis2-clustering module (again if I am not
mistaken) which we are not using.
I had previously migrated a fork of Axis2 to the Jakarta namespace (almost 2
years ago) and so I noticed that the version wasn't quite right when I started
testing the new 2.0.0 release.
I don't know any details about the migration / API changes between the
juli/tribes libraries between 10.1 and 11.0 - but of course since the
recommended Tomcat level is 10.1 there might be incompatibilities.
[~cortlepp] - Basically I was just reporting the problem - what the Axis2 team
decides to do with it ... :)
was (Author: JIRAUSER308863):
For me it is not (currently) causing problems - we are heavily basing our
dependency levels on the Spring Boot (currently 3.4.4) dependencies which are
imported as BOM in parent POM - this nails our Tomcat Level at 10.1.* currently.
It is also only imported in the axis2-clustering module (again if I am not
mistaken) which we are not using.
I had previously migrated a fork of Axis2 to the Jakarta namespace (almost 2
years ago) and so I noticed that the version wasn't quite right when I started
testing the new 2.0.0 release.
I don't know any details about the migration / API changes between the
juli/tribes libraries between 10.1 and 11.0 - but of course since the
recommended Tomcat level is 10.1 there might be incompatibilities.
> Tomcat Version too high?
> ------------------------
>
> Key: AXIS2-6090
> URL: https://issues.apache.org/jira/browse/AXIS2-6090
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 2.0.0
> Reporter: Jeff Thomas
> Priority: Major
>
> I *think* Axis2 is getting ahead of itself with regards to the Tomcat
> dependency.
> In this PR ([https://github.com/apache/axis-axis2-java-core/pull/866)] the
> level of the tomcat library was bumped to 11.0.5.
> Tomcat 11 uses the baseline described here:
> [https://tomcat.apache.org/whichversion.html]
> This includes the Jakarta Servlet 6.1 API, JSP 4.0, ... and requires Java 17
> or higher.
> From the tomcat landing page:
> "The Apache Tomcat Project is proud to announce the release of version 11.0.5
> of Apache Tomcat. This release implements specifications that are part of the
> Jakarta EE 11 platform."
> The most current spring boot version is still only supporting Jakarta EE 10
> and uses Tomcat 10.*
> *EDIT* More info about the migration from 10 to 11 - significantly the
> removal of SecurityManager code *and* the ability to configure a security
> manager in tomcat:
> https://tomcat.apache.org/migration-11.0.html
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
