I would simply lock other drag and drop upload components, while upload is in
progress.
You can also have a look at my experiments with custom drag and drop upload
fields here https://github.com/andruhon/WicketDragAndDropFileAjaxUpload
I have similar implementation in my app and it does allow
Hi Sven,
so to get this right: all wicket ajax is basically a queue where only 1
instance is worked on at a time and nothing is possible in parallel?
(but browsers and ajax in parallel is working since at least 2011? e.g.:
jQuery.when() )
You mention the upload to a resource - how would this
Hi,
Some time ago, we faced a similar issue. A custom component accessed
pages after they were unlocked, causing stale locks. Back then I filed
an issue (WICKET-6558), but haven't had time to implement the fix.
Locking pages after commitRequest should be blocked.
Best regards,
Emond
On Tue, Aug
Hi,
all Ajax behaviors' requests are queued in the browser. Even if you
disable this (see AjaxRequestAttributes#channel), all access to the page
is synchronized on the server anyway.
You could to upload to a resource instead, AjaxFileDropBehaviour doesn't
support this though.
Have fun
Hi,
PageAccessSynchronizer#detach() unlocks all pages.
Is your request logger running after that?
Have fun
Sven
On 13.08.19 07:46, Martin Grigorov wrote:
Hi,
If the page is not unlocked then it is a bug.
But it is strange that no one faced it before. This code is in use since
Wicket 1.5.0.
Hi,
wicket 8 has this neat AjaxFileDropBehaviour and it works like charm. However,
if I have multiple components on one page with a AjaxFileDropBehaviour each and
the upload of 1 drop is running, i cant upload a 2nd one at the same time; Any
idea how to solve this?
E.g.: File 1 with 100MB
