I'm pretty sure a single thread is used to service the HTTP request that
results in the rendering of the page so I would expect LDMs to be loaded
sequentially.
-Original Message-
From: Hendy Irawan [mailto:he...@soluvas.com]
Sent: Tuesday, 25 December 2012 1:00 PM
To:
Thats true, but it is easy to use a custom model to make a concurrent or
asynchronous load. We are using ASyncModels in our christmas project
(https://github.com/osiefart/wicket-christmas).
Kind regards,
Olaf
-Ursprüngliche Nachricht-
Von: Chris Colman
If you want to speedup thing, you should trigger some model loading as early as
possible.. (It is too late, if a component calls IModel.getObject() (should
return the right value)). Because wicket uses one thread per request you must
use an other thread for loading.
This way you could speedup
Thank you Olaf and Michael.
I think this is workable... We can create an abstract base class that
instead of doing load() directly, the signature would be something like:
public FutureT load(ExecutorService executor);
The async load() will execute immediately upon model creation, and during
the
Does Application getExceptionSettings().setUnexpectedExceptionDisplay(
); help?
Look at DefaultExceptionMapper (which I think you can also set in
Application.init() )
N
On Tue, Dec 25, 2012 at 3:15 PM, Chris Colman
chr...@stepaheadsoftware.comwrote:
When running in production mode and an
