which leaks? give use a real wicket example where it leaks, which isnt the thread itself thats the leak.
On Fri, May 21, 2010 at 12:49, Adriano dos Santos Fernandes < adrian...@gmail.com> wrote: > On 20/05/2010 19:14, Jeremy Thomerson wrote: > >> But it also don't break anything with the ITL, and it doesn't add more >> complexity. So, in that case, why should we remove the ITL? >> >> > It was already shown various reasons where it doesn't work well: leaks due > to *Java class library threads*; problem with multiple Wicket applications > in same web application; problem with shareable classes creating threads. > > Don't try to generalize specific problems. Before, Wicket was always in > favor of letting hooks for people do specific things, why do that evil > change now? > > > Adriano > >
