cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ralph Goers <>
Subject Re: More than one lifecycle interface
Date Tue, 18 Oct 2005 05:17:07 GMT
No, but it makes sense since they each have characterstics that are 
incompatible with each other.
SingleThreaded implies that the class is a singleton and is not thread 
safe and should essentially be executed in a serial fashion (a huge 
ThreadSafe - the class is rentrant and can be executed by multiple 
threads simultaneously.
Poolable - Each thread should get its own instance of the class and that 
there should be a pool of them from which they are doled out.


Lachlan Paterson wrote:

> Has anyone run into a problem like this?
> [CONFLICT] More than one lifecycle interface in [my class] May 
> implement no more than one of SingleThreaded, ThreadSafe, or Poolable

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message