On Sunday 01 June 2003 15:51, Carsten Ziegeler wrote:
CZ> The safest way is to lookup/release a component every time you
CZ> need it, so the fragmentextractor uses the "correct" approach.
CZ> If you know that the component you want to use is ThreadSafe
CZ> and will always be ThreadSafe than you can optimize your code
CZ> and lookup the component only once - this optimization has been
CZ> done in the xslttransformer.
XSLTProcessorImpl uses Store.TRANSIENT_STORE, like the FragmentExtractor. I
haven't mentioned this explicitly.
I have looked into the interfaces, and when I understand right, I had to look,
if store implements ThreadSafe. Store doesn't implement ThreadSafe, but the
MRUMemoryStore, which is used as default in cocoon. So I'd say it's a bug in
XSLTProcessorImpl. Agreed? What I would do, is asking in avalon-users for
changing XSLTProcessorImpl and perhaps others or to have Store implement
ThreadSafe. But I guess, Store is already released.
Regard
Torsten
--
Domain in provider transition, hope for smoothness. Planed date is 1.7.2003.
