Does somebody know why ThreadLocal is used in PoolableProxyHandler [1]
for the componentHolder in Cocoon 2.2?
Thanks, Alex
[1]
Alexander Daniel wrote:
Does somebody know why ThreadLocal is used in PoolableProxyHandler [1]
for the componentHolder in Cocoon 2.2?
Sure :)
Whenever components are taken out of the pool they need to be put back
somehow, so they are available for other clients again.
We use a thread local
On 03.07.2009, at 10:41, Carsten Ziegeler wrote:
Alexander Daniel wrote:
Does somebody know why ThreadLocal is used in PoolableProxyHandler
[1]
for the componentHolder in Cocoon 2.2?
Sure :)
Whenever components are taken out of the pool they need to be put back
somehow, so they are
Alexander Daniel wrote:
On 03.07.2009, at 10:41, Carsten Ziegeler wrote:
Alexander Daniel wrote:
Does somebody know why ThreadLocal is used in PoolableProxyHandler [1]
for the componentHolder in Cocoon 2.2?
Sure :)
Whenever components are taken out of the pool they need to be put back
On 03.07.2009, at 14:20, Carsten Ziegeler wrote:
Alexander Daniel wrote:
On 03.07.2009, at 10:41, Carsten Ziegeler wrote:
Alexander Daniel wrote:
Does somebody know why ThreadLocal is used in
PoolableProxyHandler [1]
for the componentHolder in Cocoon 2.2?
Sure :)
Whenever components
Alexander Daniel wrote
PoolableFactoryBean [2] creates a new PoolableProxyHandler instance [1]
for each pooled component used in a pipeline, i.e. it will not be shared
across different requests. Therefore I do not understand the use of
ThreadLocal.
Yes, you're right for sitemap components -
