Hi all, I'm new to the Xalan world and I'm trying to discern some information that the documentation doesn't seem to address. One of my concerns is with the ownership and lifecycle of the different objects that are returned from the Xalan library. I'm doing transformations that are returning output in a XalanDocument. The documentation does state that this object is owned by the library. Calling destroyDocument can ensure it goes away cleanly when no longer needed. I'm concerned about the other calls though.
For example, when I call getFirstChild I get a node pointer. Who owns that object? Will it live as long as the XalanDocument? When I make a call that returns a NodeList, who owns this structure? How many of these structures can I be working with at one time? Does the library own and reuse one of them or are there multiples? If it's creating them on the fly, how can I ensure these are cleaned up when I'm done with them as opposed to when the document is destroyed or the call to terminate() is made? Lastly, the semantics for the methods in XalanNode are fairly vague. If I were to call getFirstChild() on a XalanElement I can then call getNextSibling() on the resulting XalanNode to iterate through the nodes at that level in the document? What constitutes a node vs. an element? Are attributes included in the chain of nodes that are accessed in this process? I can't see the difference between getNodeName and getTagName,etc. Sorry for so many questions, but as you can see I'm finding the docs a little sparse so I need some perspective on the assumptions this API makes. Is there a more descriptive set of docs for the Xalan DOM api that I'm missing somewhere? Perhaps someone can point me in the right direction :) Thanks! -- Greg Dunko Fidelity Investments 603.791.8216 mailto:[EMAIL PROTECTED]
