Sounds good to me, so something like v2 will target legacy apps migrating to jakarta but there will be no v3 so prefer migrating to servlet API - or your env API.
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/application-development/java-ee-8-high-performance> Le mar. 11 juil. 2023 à 14:43, Dennis Kieselhorst <d...@apache.org> a écrit : > > Not sure I get the why, let me summarize: > > > > * using [fileupload] in a servlet >= 3 container is conflicting and can > > easily mess up things > > * servlet provides [fileupload] api > > * jetty (since you mentionned it) does not use [fileupload] ( > > > https://github.com/eclipse/jetty.project/blob/jetty-10.0.x/jetty-server/src/main/java/org/eclipse/jetty/server/MultiPartFormInputStream.java#L82 > ) > > but only tomcat does > > > > Pretty sure there are more, see linked JIRA tickets. I'm using it here: > https://github.com/awslabs/aws-serverless-java-container > > Let's move ahead with a release and point out in the docs that from a > consumer perspective using Servlet API is preferred. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
