czw., 29 gru 2022 o 09:01 Yasser Zamani <yasserzam...@apache.org> napisał(a): > Am I right that even if it was a servlet then it wasn't working too? as > per [1].
There is a slight problem with "keep using commons-fileupload" - it depends on "javax.servlet" package, while this package is available in the first version of JakartaEE, then it got lost in the latest version in favour of "jakarta.servlet" package and it isn't binary compatible anymore. So going away from "commons-fileupload" is a must-have in the near future. https://jakarta.ee/specifications/servlet/4.0/apidocs/ https://jakarta.ee/specifications/servlet/5.0/apidocs/ Anyway, I already found a solution to keep using Struts filters and @MultipartConfig, PR to come :) > Anyway in general I think we shouldn't try to keep supporting both. > "Java EE is Officially Retired. It’s Now Called Jakarta EE. How Did We > Get Here?" [2]. > > So I think at some day we may have a release that switches fully over > and is not backwards compatible - obviously things like > commons-fileupload which aren't able to switch have to be replaced. It's not that easy (I already got emails from enterprises about moving from Servlet 2.4 to Servlet 3.1) and to be honest I prefer to have Struts "servlet agnostic" which can be achieved with some additional work. Basically the whole Core has to avoid using javax.servlet/jakarta.servlet and I already started working on that, hopefully it will be done in Struts 7.0.0 :) Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
