I think Ernesto suggests to use something like the mounted resources explained at http://wicketinaction.com/2011/07/wicket-1-5-mounting-resources/ This way the browser will be able to make several requests to the server because there is no locking at the server side as with Page instances.
Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Thu, Jun 4, 2015 at 10:43 AM, Edgar Merino <[email protected]> wrote: > Hello, thanks for the response, what do you mean exactly by delegate to > the mounted resource? I'm thinking I can mount the images resource, and > simply reference them using their URI (is this what you mean by delating > the call to the mounted resource?), so even if users replace the panel, > image loading won't be cancelled, since it will still be waiting for an > existing resource (instead of the problem I'm having now, where the > resource vanishes before being transfered to the user). > > I believe this should avoid 3. in your response, what do you think? > > > On 04/06/15 02:26, Ernesto Reinaldo Barreiro wrote: > >> Hi, >> >> I see two options.... >> >> 1- Block the screen while images are being loaded so user has to wait. >> >> or >> >> 1- Mount a resource serving images thumbnails. >> 2- Panel showing those thumbnails just delegates into mounted resource. >> So, >> image generation will be faster and panel replacement will be more fluid >> 3- Also block UI while replacing panel: if your users are too fast you >> might encounter the same problem again. >> >> >> On Thu, Jun 4, 2015 at 9:16 AM, Edgar Merino <[email protected]> wrote: >> >> Hello: >>> >>> I'm having a problem with dynamic resources and ajax calls, I have a >>> panel that includes some image thumbnails, these thumbnails may take >>> between 5 and 30 seconds, if a user attemps to cancel loading of this >>> images and loading another panel (e.g. replacing the panel), an exception >>> will be thrown and cause a 500 response for each of the resources that >>> failed to load. The logged error message is as follows: >>> >>> ERROR - DefaultExceptionMapper - Unexpected error occurred >>> org.apache.wicket.WicketRuntimeException: Component >>> 'mainContainer:mainPanel:wrappedContent:tabbedPanel:panel:materias' has >>> been removed from page. >>> >>> I understand the error, but I don't know what to do to avoid it, has >>> anyone got a similar problem and found a solution? >>> >>> >>> Thanks in advance. >>> Edgar Merino. >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >>> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
