Again I know nothing about Avalon, but there seems to be some conceptual confusion between "Stateless" and "ThreadSafe". Stateless objects are of course thread-safe but stateful objects may be also. A container that automatically turns a "ThreadSafe" component into a singleton seems broken to me. Rather I would have thought that a container would provide synchronization to such components.
Your're right, and IIUC, Fortress now uses the "singleton" term for "ThreadSafe", which seems more appropriate.
See bottom of http://avalon.apache.org/excalibur/fortress/using-meta-info.html
Sylvain
-- Sylvain Wallez Anyware Technologies http://www.apache.org/~sylvain http://www.anyware-tech.com { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects } Orixo, the opensource XML business alliance - http://www.orixo.com
