Please open a ticket, I will try to reproduce and upload a quickstart. I remember of it taking some time to be hidden, but just the time of form submit process (maybe your form do heavy processing, easily reproducible on quickstart).
On Mon, Apr 4, 2011 at 12:43 PM, <mzem...@osc.state.ny.us> wrote: > Sorry but I do not have the time/resources to create a quickstart (I don't > use Maven) but I wanted to alert the group to an issue I had in case > anyone wanted to test/fix it. > > Using the following; > > Wicket 1.4.16 > UploadWebRequest in App object > Form with setMaxSize() (I'm using 1MB) > FileUploadField > AjaxSubmitButton > UploadProgressBar > > When the form max size exception is hit, the progress bar stays visible > and refreshes many times showing no progress, then eventually disappears. > If I manually call error on a component the form stops processing and the > progress bar disappears as expected. I'm not sure if the bug is in the > progress bar or the form processing. There also seems to be some > difference between Wicket 1.4.16 and 1.4.15. Using 1.4.15 the progress > bar disappeared but the page continued to refresh repeatedly. After > upgrading to 1.4.16 the progress bar remains visible and continues to > refresh erroneously. > > > > Notice: This communication, including any attachments, is intended solely > for the use of the individual or entity to which it is addressed. This > communication may contain information that is protected from disclosure > under State and/or Federal law. Please notify the sender immediately if > you have received this communication in error and delete this email from > your system. If you are not the intended recipient, you are requested not > to disclose, copy, distribute or take any action in reliance on the > contents of this information. -- Pedro Henrique Oliveira dos Santos
