Vadim Gritsenko wrote: > >Now, the optimization I was refering to can only take place *if* you > >know which implementation for a component is really used and *if* > >this specific implementation is ThreadSafe. This is a dangerous > >assumption! If you assume a component is implemented in a thread safe > >manner and this changes sometime and you don't reflect these changes > >than you will quickly result in threading problems. > > > > Not in this case though. I think you forgot that XSLTProcessor is > Recyclable, and not ThreadSafe. > no :) - my comment was meant in general and not targetted at the store, but yes, you're right, it's only dangerous if the own component is ThreadSafe.
Carsten
