Can you explain what is the reason for using a background-thread?
Depending on your container you might want to use e.g. Continuations or
Servlet-Async to compute lengthy values in the background and then let
render the page as normal in the RequestCycle depending on that result.
Am 28.05.2015 11:51, schrieb Peter Henderson:
Hi
I am trying to render a component in a background thread.
My first attempt fails with an Exception
"There is no application attached to current thread Thread-4"
So I link the application with the background thread and now a different
exception.
java.lang.IllegalArgumentException: Argument 'requestCycle' may not be null.
at org.apache.wicket.util.lang.Args.notNull(Args.java:41)
at
org.apache.wicket.Application.fetchCreateAndSetSession(Application.java:1568)
at org.apache.wicket.Session.get(Session.java:171)
Is component renderer designed to work from a background thread?
I've put a quick start on git hub.
https://github.com/bollinger/wicket-ComponentRenderer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
