i still dont see your solution about the wicket thread class.
What should that one do??? give an example.
The best solution is to use a threadpool like a described above.
And yes that InheritableThreadLocal isnt needed then.
But using
final Application app = Application.get()
// start thread
is exactly the same kind of leakage as using InheritableThreadLocal
On Thu, May 20, 2010 at 12:38, Adriano dos Santos Fernandes <
adrian...@gmail.com> wrote:
> On 19/05/2010 22:29, Jeremy Thomerson wrote:
>
>> It solves this problem, which is specifically why it was requested:
>>
>> onClickOrSomethingSimilar() {
>> new Thread(new Runnable() {
>> void run() {
>> doSomethingWith(Application.get());
>> }
>> }).start();
>> }
>>
>>
> That's what I said about have a WicketThread class, or "publish"
> Application.set/clear for users do this with more safety.
>
>
> Adriano
>
>
