I've added the upload progress to the examples in 1.5.x too. Works fine here now.

I thought so . But I tried it again. Both cases worked fine . So I'm happy. I would more happy if you could backport this nice feature into 1.5.x branch .

You've forgot getApplicationSettings().setUploadProgressUpdatesEnabled(true);

Quickstart project for testing WICKET-4623

Okay. I made a quickstart cut off my upload form's relevant part and tested it. (I use 1.5.x branch so I could not try it in my project). Now I'm a little bit confused. Progressbar shows up in both cases (even with AjaxLink or Button) but does not show the progress. Moreover if I try to upload a bigger file to see the progress the bar disappears after few seconds.
It might be something wrong with my quickstart I don't know. Attached it. Please check.

Sven Meier

Sure. Give me some time pls.

I've checked in a small fix needed on master for the progressBar to hide again on Ajax upload.

@Sandor
Could you please check whether the problem still persists?
After much tinkering with Ajax upload I don't understand how the actual upload can be delayed to arrive after the first status update, which is fired at least 1 seconds later.
In my tests I was able to reproduces this only if I put a breakpoint in the upload processing, thus preventing storing of UploadInfo in the session before the status update request tried to look it up again.

Update progressBar on ART and just let UploadStatusResource running even if no UploadInfo available.

Note that MultipartServletWebRequestImpl uses #getUploadInfo() itself. So in rare cases it could mark the uploadInfo as readOnce and remove it from session already before the UploadStatusResource has accessed it. Wouldn't that make the progressbar running forever?

What about making ProgressBar smarter (i.e. let it extend FormComponentPanel) so that it updates itself on ajax form submit? No need then for the UploadStatusResource to signal the end of upload. It could just return "0|" when no info avaiable, as you've changed it.

Here is a "solution" that keeps the UploadInfo in the HttpSession until it is read at least once.

The problem is that this way it may leak but it has just 3 'long' fields and one 'boolean'.

I've added a progressBar to example's FileUploadPage (don't forget getApplicationSettings().setUploadProgressUpdatesEnabled(true)) and can confirm the issue.

Problem is that the request for the upload status (UploadStatusResource) is coming in earlier than the actual upload via ajax. Thus no UploadInfo is found in the session and the progressBar assumes the upload to have finished.

A the moment I don't have an idea how to fix this.