On 19/05/2010 18:46, Martijn Dashorst wrote:
I wondered about this too: would this work with a job framework like
Quartz? The thread is not started in a wicket context, but by the
thing that quartz is managing. Therefore the inherited thing would not
work and the Application would not be set.
I do not know Quartz, but I suppose a lot of problem can arrive if the
library is shared by all applications.
If its thread pool starts during a request, all of its created child
threads will have a reference to the initial application, even when
running jobs of others applications.
Adriano
