Re: WICKET-2846 - Store Application in InheritableThreadLocal instead of ThreadLocal

[Jeremy Thomerson]

>
>
> To clarify this, I use Application.set and Application.unset there.
> Although public, they're "not part of Wicket public API". So IMO, the
> initial issue would be better done making these methods part of the public
> API.
>
>
And then people all over will have memory leak issues because they'll forget
a finally block.  We tell you those are not part of the public API because
you should *not* use them.  If you want to use them that way, then fine, but
you have to deal with the consequences - not us.