OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Garbage collection in DOM

[ Lists Home | Date Index | Thread Index ]

I'm writing an application using the Java binding of DOM (Xerces,
but I'm trying to use the JAXP framework and generic DOM interfaces/methods
as much as possible to avoid tying myself permanently to a specific DOM 

What I was trying to determine was whether there is a way to "destroy" a
(or even a complete Document) after having created it. My application is
multiple transforms and basically handing off one Document (or Node
from one Transformer to the next. As I go through several transformations,
like to get rid of the Transformed subtrees as I go.

My current design "hands off" a node from one Transform to the next and
currently each of the nodes are children of the same document. Once I
a transformation, its "source Node" will no longer be needed as I go down a
chain of Transforms. I know you can do a "removeChild" to remove a Node
from wherever it was inserted into the tree, but there still seems to be an
association to the owner document. Is there a way to "break" that
so that once the Node is no longer needed, all references to it can be
so that it will be garbage collected?

I want to try to avoid any XML Parser/DOM Implementation-specific calls if
all possible.

Jim Harmon


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS