Hi,
Am I right that even if it was a servlet then it wasn't working too? as
per [1].
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.
Regards
[1] https://stackoverflow.com/q/14443148/1362623
[2]
https://jakartaee-ambassadors.io/2018/03/02/java-ee-is-officially-retired-its-now-called-jakarta-ee/
On 12/28/2022 4:47 PM, Lukasz Lenart wrote:
Hi,
As I'm looking into supporting both worlds - JavaEE & JakartaEE -
there are some problems with file upload support. commons-fileupload
doesn't work with JakartaEE and migration to pure Servlet API based
solution requires using @MultipartConfig annotation on the servlet -
yet Struts uses a filter which isn't supported.
Any idea how to overcome this?
https://stackoverflow.com/questions/68820707/jetty-11-and-commons-fileupload
Regards
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org
