On 21/05/2010 11:24, Jeremy Thomerson wrote:
So, again, what you're saying is "if you already
have a broken application, it will stay broken". Okay, I'm fine with that.
I would have to make more hacks as clear/re-set wicket application, to
not leak *more* things that it leaks by default. The Java bug (related
to context classloader) leaks only classes (and static instances).
Without do more hacks, it will also leak a chain of objects reachable by
Application (and user's extended class).
James explained better than me the other issues. I'd say it's much
better to offer hooks (and it's Wicket tradition way) than to put
something invasive in the core.
You also said about release 1.4.9 and delay a change. Well, once you
make users not worry (in theory) about the application in TLS, you're
going to make then angry if you revert it.
I'm now shutting-up. I've said many times all the issues it's going to
cause. It's the committers that have the final word, anyway...
Adriano
