Interesting approach. Our use case is more complex, as it runs a
background task in a separate thread. Our task has three basic
requirements. It must:
1. Be cancellable.
2. Report its outcome (success/failure/warning).
3. Report incremental progress.
Our fundamental problem is not how to
Hi,
You can put the tasks in an application scoped structure (e.g.
MyApplication.get().getTasksMap()) and use a serializable key.
Martin Grigorov
Wicket Training and Consulting
On Tue, May 6, 2014 at 2:11 PM, Richard W. Adams rwada...@up.com wrote:
Interesting approach. Our use case is more
Hi,
On Tue, May 6, 2014 at 2:11 PM, Richard W. Adams rwada...@up.com wrote:
Interesting approach. Our use case is more complex, as it runs a
background task in a separate thread. Our task has three basic
requirements. It must:
1. Be cancellable.
2. Report its outcome
.
What is the 'context' class you refer to? Where is it instantiated and
where is it stored?
From: Ernesto Reinaldo Barreiro reier...@gmail.com
To: users@wicket.apache.org users@wicket.apache.org
Date: 05/06/2014 07:52 AM
Subject:Re: Background Threading
Hi,
On Tue, May 6
reier...@gmail.com
To: users@wicket.apache.org users@wicket.apache.org
Date: 05/06/2014 07:52 AM
Subject:Re: Background Threading
Hi,
On Tue, May 6, 2014 at 2:11 PM, Richard W. Adams rwada...@up.com wrote:
Interesting approach. Our use case is more complex, as it runs
