You could execute calls in a background thread, yes i know java ee warns about this, but i think it actually is a better solution then having your user wait. That way the user can continue to work and periodically check a special page which shows the progress of the task with some fancy ajax progressbar.
Maurice On Wed, Apr 23, 2008 at 9:40 AM, Rens Verhage <[EMAIL PROTECTED]> wrote: > There's also the AjaxLazyLoadPanel in wicket-extensions. > > Rens > > > > > On Wed, Apr 23, 2008 at 9:19 AM, lars vonk <[EMAIL PROTECTED]> wrote: > > > @1: There is also the session timeout of your appserver (I think the > > default > > for most app servers is 30 minutes).... In my experience it is not very > > user > > friendly if pages take that long to render... A better approach is I think > > to use some Ajax stuff as you describe in your second question. > > > > @2: There is a progressbar component available in wicketstuff: > > > > http://wicketstuff.org/confluence/display/STUFFWIKI/wicketstuff-progressbar > > . > > I don't have any experience with it though... > > > > Hope this helps, > > > > Lars > > > > On Wed, Apr 23, 2008 at 5:09 AM, PhilipJohnson <[EMAIL PROTECTED]> wrote: > > > > > > > > Greetings, Wicket Wizards, > > > > > > I am continuing my delightful acclimatization to Wicket, and would > > > appreciate a couple of quick hints regarding the following: > > > > > > (1) My webapp makes several requests to back-end services. This could > > take > > > up to a couple of minutes under certain circumstances. It appears that > > > Wicket times out a page request after one minute. (?) How do I tell > > > Wicket > > > to wait longer? I did some googling and found the > > > IRequestCycleSettings.setTimeout(Duration) method, but the documentation > > > did > > > not make me confident that I'd found the right thing. > > > > > > If that is the right method to call, how do I obtain the instance to > > > invoke > > > the setTimeout method on? Any other timeout issues I should be aware > > of? > > > > > > (2) Since certain of my pages make a series of back-end service requests > > > before responding, it would be cool if I could have a kind of "status" > > > pane > > > that tells the user how far along the webapp is. Given that Wicket > > tends > > > to > > > make hard things easy, I'm fantasizing that I could create some kind of > > > Ajax-y pane that refreshes itself periodically with the contents of a > > > String > > > that I keep in my session instance. Then, as my internal page > > processing > > > code works through the backend requests, the code can just update that > > > string and it will be displayed to the user. > > > > > > Is that possible? Any pointers to classes/code I could look at to > > orient > > > myself? > > > > > > Thanks so much! > > > Cheers, > > > Philip Johnson > > > -- > > > View this message in context: > > > > > > http://www.nabble.com/Request-for-hints%3A-Long-duration-requests--ajax-%27status%27-line-tp16830536p16830536.html > > > Sent from the Wicket - User mailing list archive at Nabble.com. > > > > > > > > > --------------------------------------------------------------------- > > > 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]
