On 3/27/24 06:13, Romain Manni-Bucau wrote:
Le mer. 27 mars 2024 à 10:58, Rémy Maucherat <> a écrit :

On Wed, Mar 27, 2024 at 9:49 AM Romain Manni-Bucau
<> wrote:

Hi all,

Checkout out TomEE's notifications I realized Tomcat is in a weirdish
situation where Tomcat 9 is Servlet 4 and "+1" version is Tomcat 10.1
is Servlet 6.
It means Tomcat is no more a Servlet 5 friendly option.

I wonder if it means Tomcat < 10.1 should be stopped too or if Tomcat
should be maintained and released again - pretty sure we can find help if
desired for that not that far.
Another option is to restore the deleted methods between servlet 5-6 in
code base to be able to run Tomcat 10.1 with Servlet 5 API instead of
Servlet 6 - to pass signature TCK.


Nothing. The Tomcat developers (= the committers) determined that the
EE 9 release was useless since the only change is the javax -> jakarta
package renaming. A big task for sure, but that seemed to us this was
more a developer oriented armaggeddon and not something that benefits
our users.

For reasons that elude my understanding, some other projects like
TomEE thought this was still useful and decided to release full
support for EE 9 rather than go to EE 10 like we did. Our plan about
EE was public. So I guess this is still our problem obviously, but I
don't feel like doing anything about it.

 From what I saw on other AsfEE projects, users requested it, nothing more
and then you have CVE game.

BTW, about the last item. Recently, I tried to run CXF on the new EE
10 APIs (since OWB moved to that). It doesn't work as it uses
deprecated APIs, while IMO it should have moved away from them long
ago. And it's an ASF project, not some hack project somewhere.

This is fixed AFAIK on master (maybe last release, didnt check) so should
be fine soon.

Basically unless there's a cut somewhere, nothing will ever change :D
As a result, I don't think an API restoration in Tomcat 10.1 is a good
idea ...

Ok, so last option is TomEE community taking the lead on 10.0 branch, is
that an option if all the PR work is done?

Is the problem that you have customers actually using these APIs?

Or is the problem that you can't pass a TCK unless you have support for these ancient methods?

Most of that stuff was deprecated ages ago and just finally removed.

Why is it super important for you to get certified for Servlet 5 specifically? Why not just get Jakarta EE 10 certified and move on? Any applications that would actually fail on Tomcat 10.1 + Migration Tool really really _really_ need to be updated to work properly. People have had 15 years to stop using that stuff.

Honestly, I think it would be much more worth you while to fork Tomcat 10.1 and add-back the methods you need rather than trying to resurrect the 10.0 branch. There have been no commits on that branch for 2 years, and we've had something like ~24 releases of each other branch in the meantime. That includes performance improvements, security fixes, feature and stability improvements, etc.

Would it be as simple as providing your own replacements for deprecated classes/methods to pass the TCK? That seems far less onerous than bringing back zombie Tomcat 10.0.


To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to