RE: [picocontainer-dev] While looking at the streamlining of NanoWar ...

> ... and given my task is to replace 'one container per session and one
> container per request' with three 'static' containers + some
> threadlocal store magic ...
> 
> ... a problem is that start()/stop()/dispose() will have to be
> rethought for session and request scoped components.

> 
> Do people use lifecycle for session or request scoped components?

Actually Hibernate components use lifecycle for request scoped components.  The
idea is that there's a Hibernate session automatically created during the start
of the request and closed at the end. 

This type of behavior is very useful for creating components that would normally
have to be initialized through a web filter.  (See Able project's transaction
filter as an example)



								-Mike


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email