Re: [picocontainer-dev] Patch for web ... to close that static getter IoC problem

>>
>
> Correct.  In fact, I _thought_ that's what you were going to do with  
> your last
> refactoring of pico-web.

We still could do that as well.

>
>
>> Then as http requests happen, pre-process the whole container,  
>> setting
>> the right cached session scoped things, and ensuring that none at the
>> request level are cached.
>
> And that's exactly what the ABORT_TRAVERSAL feature of visitor was  
> added for: So
> you can process the app-level container for components without  
> accidentally
> pre-processing any child containers.
>
> Of course, you would still need the ThreadLocal so each request- 
> level component
> adapter instance would know where to store its stuff since  
> ComponentAdapter
> instances would be shared across requests.  (Which I think, is what  
> you're
> trying to say :) )
>

:)

> That said, you wouldn't need a ThreadLocal for the current application
> container, like you do in PicoServletContainerFilter, would you?

We're not setting the app container to be thread-local managed, it's  
classic new Caching() right ?

- Paul