Hi Markus, do you have a test case about that ?
Basically, you are implementing a servlet with input data ? What I did in Pax Web is to configure the RFC compliance. It should be enough (depending of use case), so I would like to add a example/test case in Karaf (to include in itest). Thanks, Regards JB On 15/01/2020 14:42, Markus Rathgeb wrote: > I am using the following workaround: > > * fetch the upstread jetty-utils artifact > * edit the manifest and remove the exclude statement > * publish the modified artifact with another group ID to a maven repo > * use org.apache.karaf.features.xml to replace the upstream > jetty-utils with the modified one > > That way the old deprecated excluded but still used > MultiPartInputStreamParser is found again. > > I just wonder why it still occurs in the Pax Web release that > configures to use the other new multi part implementation. > Perhaps the fix is not fully complete? > > Am Di., 14. Jan. 2020 um 21:26 Uhr schrieb Markus Rathgeb > <maggu2...@gmail.com>: >> >> The bundle that handles the upload specific part does not depend on >> any Jetty specific bundle / package. -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
