Using GAE/J deferred tasks in Apache Wicket

[Ian Marshall <Ia...@GMail.com>]

I have tried using Google App Engine for Java (GAE/J) deferred tasks in
Apache Wicket.

They do indeed run, but I cannot access the bulk of my data exchange code
since it needs the context of an application and/or a session to work. I
presume that the underlying cause of this is because when the task fires, it
calls a default servlet as opposed to one of my web pages (which results in
the page's code running in the context of an application and a session).

I have reverted to using GAE/J enqueued tasks to fire up a web page and do
my processing from there. But I was interested in using DeferredTask since I
wanted to:

  ·  bypass the GAE/J 30-second web page response limit and use the GAE/J
10-minute task processing limit instead
  ·  obviate having to code new web pages and just implement the
DeferredTask.run() method.

Has anyone got to use DeferredTask within the context of an application and
session successfully?

--
View this message in context: http://apache-wicket.1842946.n4.nabble.com/Using-GAE-J-deferred-tasks-in-Apache-Wicket-tp3578949p3578949.html
Sent from the Users forum mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org