Unfortunately we are unable to test M6. We upgraded to M5 but found out that Wicket uses M4. And there has been aan incompatible change from M4 to M5: set...Max(...) → setMax...(...) in JakartaServletFileUpload. The Wicket code has already been changed, but this has not been released yet.
We also made change to the locale settings of the container and that helps. The path is stil checked but (almost all) paths are now considered acceptable. Regards, Johan ________________________________ Van: Gary Gregory <[email protected]> Verzonden: dinsdag 24 maart 2026 16:15 Aan: Commons Users List <[email protected]> CC: Stuyts J. (Johan) <[email protected]> Onderwerp: Re: M6 release so FILEUPLOAD-362 can be avoided? Hello Johan, Please test with 2.0.0-M6-SNAPSHOT from the snapshot Maven repository (https://repository.apache.org/content/repositories/snapshots/) and let us know here if you find any other issues. Then, I can plan to create a release candidate. Thank you! Gary On Tue, Mar 24, 2026 at 5:37 AM Stuyts J. (Johan) via user <[email protected]> wrote: > > Hi, > > I am using the latest Wicket release and running into > https://issues.apache.org/jira/browse/FILEUPLOAD-362. I see that milestone > releases happen about twice a year. Is it possible to release M6 sooner? > > It is probably possible to hack something together that prevents the > exception from being thrown. But turning that into solution with a good user > experience will be quite some work. It would be great if can avoid that. > > Kind regards, > > Johan Stuyts > Senior developer > Mijn Loket team, Municipality Rotterdam > > > ________________________________ > Heb je vragen over deze e-mail? Neem contact op met de afzender. > Is deze e-mail niet voor jou bedoeld? Laat het de afzender weten en verwijder > de e-mail > U2FsdGVkX1+Abz9GMQwAz8frDzYnT/SDimJCtD5VzmI=
