I'm using Xalan in a program which runs as background process on a unix machine. The program creates a document builder and calls transform with the builder as input (afterwards the builder is destroyed by call of destroyDocumentBuilder). This works well. But I've observed that the size of the process data grow with each call of this service. When I suppress both steps - the creation of the document builder and the transform call - the size of the process keeps stable. As the process has got to run stable for months this is an unwanted feature. Is there a reason (other than a bug) for this behavior and is it possible to avoid it? (I don't want to initiate the XalanTransformer each time, I'm in a time criticial ambiance.)
Thank you
Tobias
--
