Hi! IIRC, there's one default method on the public API (Engine?) that relies on javax.servlet. Not that it would break any existing plugin or filter, but it's part of the public API anyway. And maybe from the Session you could grab the http session as well, I'd have to look to be sure. Regarding the migration, it shouldn't be much more than changing imports, but we'll see when we are there
In any case, going to JDK-17 and requiring a new major version of Tomcat, or whichever, would be a stronger reason to name it 3.0. I remember the attempt at 3.0, but given the amount of time that has passed I think it would be ok to stick with it. At least, I'd find weird the change from 2.12 to 4.0 out of the blue. cheers, juan pablo On Thu, May 30, 2024 at 6:27 PM Foster Schucker <fos...@schucker.org> wrote: > > I've been a JSP Wiki user since the early days. I'd also suggest going > to 3.0 or 4.0 for a change like this. > > /Tomcat, Openliberty and JBoss EAP 8 are fine with 17, I hope all > applications do, too./// > My office has a sign "Hope is not an engineering strategy" :-) > > Thanks! > Foster > > >
