Saxon

Legacy ID: #5243060 Legacy Poster: Michael Kay (mhkay)

I suspect the problem is that the Ant task, when transforming many input files using the same stylesheet, reuses the JAXP Transformer object rather than the Templates. With Saxon, it's best to reuse the Transformer if the two transformations access the same source documents, but to create a new Transformer from the Templates object otherwise. But the Ant people, of course, are more familiar with Xalan which may have different optimizations. Unfortunately Saxon's AntTransform task inherits this behaviour so it won't help you. But you could try fixing it yourself at source.

Legacy ID: #5243159 Legacy Poster: Tomas Jetelina (smrk)

Thanks for swift response. Xalan has similar problems with caching. I was afraid of your solution :) To get source compiled in debugger with no error requires lot of downloading additional libraries. And with Saxon for Java even .Net stuff :( I will try to modify Ant Trax source (or rewrite xsl to java, cause I already failed with Xalan :).

Legacy ID: #5243273 Legacy Poster: Michael Kay (mhkay)

Saxon's AntTransform class is a single-class product, you don't need to build the whole of Saxon. In fact, I've done the source code changes but haven't yet tested them - if you raise an entry in the "support requests" tracker then I'll attach the untested source in my response.