Hi Thomas, that's true*, although Fulcrum "upload" is still integrated as a service by default/by example in Turbine and provides some convenience settings for fileSize et al. to wrap commons file upload (servlet). We may still keep it in servlet 6 containers as commons provides a servlet 6 compatible upload servlet. Nevertheless I already removed (commented) portlet api from dependencies.
Best regards, Georg * I recapitulate: org.apache.turbine.services.rundata.DefaultTurbineRunData.getParameters() does use ParameterParser.setRequest, where parserService.parseUpload is called. -----Ursprüngliche Nachricht----- Von: Thomas Vandahl <[email protected]> Gesendet: Freitag, 14. Juni 2024 15:33 An: Turbine Developers List <[email protected]> Betreff: Re: Question on updating Turbine core Hi Georg, > Am 14.06.2024 um 12:06 schrieb Kallidis, Georg <[email protected]>: > > Additionally Fulcrum Upload has some more migrations: > - We have to use the new dependency commons-fileupload2-jakarta-servlet6 > nevertheless. > - There is a dependency to Portlet API, should we support this anymore? It > might be much easier to drop this. My understanding is that Fulcrum-Upload is no longer necessary. I implemented Parts handling in Fulcrum-Parser long ago. Bye, Thomas --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
