The previous post refers to C++ processor. Sorry I didn't notice that the maillist is shared by both C++ and Java projects. In Java such problem doesn't exist due to automatic garbage collection. An implementation of interface org.w3c.dom.Node can create new isntances of the class which will be later reclaimed by GC. In C++ however instances allocated on heap should be explicitly deleted. In my case the sooner I free the memory the better, in other words I wouldn't want to wait for the end of transformation to delete all the objects that were created along the way. The best policy would be to keep only the objects that are currently being used by XSLT transformer.
Thanks
