You will still need client initiated requests to get your
"non-stop-updates" from the page/component to the browser. Hence, just
separate the work (which you can do continuously in your thread) from
the page rendering (which will need to be initiated by a browser request
whatever you do). Will make your live so much easier if you cleanly
separate those two tasks...
On Tue, Feb 21, 2012, at 04:48, BayPhilip wrote:
> Actually this is not my problem. You update component just once after
> some
> time while I need non-stop updating. I found a "semi-solution". I am
> using
> ScheduledThreadPoolExecutor.
>
> final ExecutorService service = new ScheduledThreadPoolExecutor(100) {
> protected void beforeExecute(final Thread t, final Runnable r) {
> Application.set(getApplication());
> }
> protected void afterExecute(final Runnable r, final Throwable t)
> {
> Application.unset();
> }
> };
> service.submit(chat);
>
> but......the thread is submitted, but it is not executed. I'm debugging
> and.....there is nothing that calls my run() method in my thread. So how
> can
> execute this thread which is submited in service.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
