MultipartServletWebRequestImpl receives 'maxSize' at [1]. And sets it later to the fileUpload at [2].
1. https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/protocol/http/servlet/MultipartServletWebRequestImpl.java#L124 2. https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/protocol/http/servlet/MultipartServletWebRequestImpl.java#L164 Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Wed, Oct 22, 2014 at 11:19 AM, Roman Grigoriadi < roman.grigori...@gmail.com> wrote: > Martin, thank you for your responses, but I don't think you understand > what I > am asking about. > > My question was purely about Wicket API, not about how containers > implementing receiving request stream. I am not trying to stop container > processing input stream. I want to tell user in an ajax response, that one > of attached files was too large. I actually know how to do it other way, > but > again, I started this thread, because I want to use FileUploadBase's > maxFileSize, which is purely Wicket business, but it seems there is no way > to propagate parameter in, as MultipartServletWebRequestImpl doesn't > receive > in constructor any. > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/org-apache-wicket-util-upload-FileUploadBase-fileSizeMax-tp4668001p4668023.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
