Hi Dave! Thanks for your advice!
> I don't know your exact design/architecture, but I would urge you to > consider giving each function instance its own XalanSourceTreeDocument > instance and installing multiple instances. It's much cleaner, and you > avoid the problem of using one XalanSourceTreeDocument instance for all > threads. Hm, you're probably right. I'll try this approach. > It's much easier to give each function instance its own > XalanSourceTreeDocument instance, and let the function instance be > destroyed after the transformation is complete. What is the livecycle of an extension function? Will a new instance be created (via clone()?) for each transformation and destroyed right afterwards? Are there significant difference in handling for globally and locally installed extensions? Thanks in advance for your time Cheers, Wolfgang -- Wolfgang Schell [EMAIL PROTECTED] GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net
