Robert McIntosh wrote: > > One that maintains no client/caller state between method invocations, > just like EJB Session beans (stateless ones obviously), and they > certainly have a lifecycle to them. In avalon a component could be > Configurable, Initializable, etc., all of which are lifecycles.
Basically you're saying that components following the IoC pattern are stateless by definition. The caller maintains state, not the callee. In web applications, however, stateless means also thread-safe (many clients on one URL simultaneously). And lifecycles tend to kill thread-safety, so you need to pool. But the original poster wanted singletons. Ulrich --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
