On Wed, May 19, 2010 at 4:30 PM, Adriano dos Santos Fernandes < adrian...@gmail.com> wrote:
> I do not think the application object is general enough to be passed > implicitly to threads. > Now, this is a valid argument! I agree wholeheartedly that Application.get() shouldn't be accessible to child threads by default. But, it's just my opinion about how to design applications and deal with thread issues, not some fundamental flaw. Anyway, the InheritableThreadLocal doesn't seem to cause any memory leak issue that wouldn't already occur due threads running amok. If the maintainers don't see a problem with it, I think this is an non-issue.
