On Sun, Aug 16, 2009 at 11:32 AM, Jerome Louvel <jerome.lou...@noelios.com>wrote:
> In your case, it seems that Application.getCurrent() returns null because > the calling thread isn't the one that was initially processing the call, > but > a Quartz worker thread instead. I don't know enough about Quartz to give details, but after a quick scan at the Quartz javadocs, I bet that a technique similar to that used in Restlet's TaskService class could be used to wrap a Quartz Scheduler to make sure that all Jobs execute with a current Application. --tim ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2384083