|
From: Stefan R. <ste...@gm...> - 2026-03-05 20:38:11
|
Yes, ModJy has been updated accordingly, see https://github.com/jython/jython/pull/414/changes. However, this has mainly been tested within Jython's normal tests and regrtests, not explicitly with other frameworks, Tomcat, etc. You should absolutely test it with your setup. There will be some beta release I suppose. If you can, ideally test it right away against current master. The earlier there is feedback on issues, the more time we have to fix it. Best Stefan Am Do., 5. März 2026 um 18:08 Uhr schrieb Chris Clark <chr...@ac...>: > > I'm guessing ModJy will be (has been) updated to support this? > > My usage is quite simple: deploying a WAR file under Tomcat so I think this will work for me (with a maybe few XML changes) :-) > > Clarification on the referenced issue/PR, these ones? > > * https://github.com/jython/jython/issues/382 - Java EE Servlet Namespace Has Been Changed From javax.servlet to jakarta.servlet > * https://github.com/jython/jython/pull/414 - Perform the jakarta EE migration > > Thanks for the heads up :-) > > Chris > > On Thu, Mar 5, 2026 at 8:06 AM Stefan Richthofer <ste...@gm...> wrote: >> >> Dear Jython users and developers, >> >> with this email I announce that the next Jython release 2.7.5 will >> change javax.servlet namespace to jakarta.servlet. If you rely on this >> for a legacy setup, the new release won't work for you as a drop-in >> replacement out of the box. Please be sure to check your setup >> carefully before upgrading. (As of this writing, no release date is >> settled. This is just an early warning to minimize surprises.) >> >> For this change, we are relocating the classes >> >> - org.python.util.PyServlet >> - org.python.util.PyFilter >> - org.python.util.PyServletInitializer >> >> to a new package org.python.servlet. >> AFAIK, frameworks usually locate servlet classes automatically, so >> this should not cause much trouble. Still, please check that your >> setup accommodates this change if necessary. The relocation allows you >> to add the old classes (with javax-based imports) on top of jython.jar >> to the classpath without name conflict. In some cases, this may be >> sufficient to retain workability of a legacy setup. For details, see >> issue #382 and pull-request #414. >> >> That said, please check the list of open issues to see if there is >> something you consider a release blocker or something you might want >> to provide a pull-request for. E.g. if someone knows how to fix #349, >> please join that discussion. >> >> >> Best >> >> Stefan >> >> >> _______________________________________________ >> Jython-users mailing list >> Jyt...@li... >> https://lists.sourceforge.net/lists/listinfo/jython-users |