Scott Eade wrote: > Does this change have any other implications? I don't think so. Actually the whole thing was probably caused by a brain knot of mine, mixing up single threaded with singleton. In an Avalon container such as ECM the difference is important because it defines not only the life cycle of a component but also the life style.
As TorqueInstance is used as a thread safe singleton, TorqueComponent should work the same way. I'll fix this in SVN. Thanks for taking the time for digging into this. Bye, Thomas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]