On Tuesday, 08/12/2003 at 04:54ZE12, [EMAIL PROTECTED] wrote:
> I have a stylesheet extension that relies on ability to do
> getElementsByTagName on an element
Basically, the implementation chosen depends on what kind of data you pass
into Xalan. If you hand us a SAXSource or StreamSource, we build a native
DTM, and tne have to generate DTMNodeProxy objects when an extension wants
a (subset of) DOM view of the data. If you hand us a DOMSource and we use
DOM2DTM to wrapper it (currently only the case in interpretive Xalan),
requests for DOM nodes are handled by unwrapping them rather than by
applying another layer of wrapper.
So, yes, if you do DOM based transformation you'll probably bypass the
current limitation in our DTMNodeProxy layer. Of course there are some
performance issues involved in that approach; we burn more memory when
running from a DOM than when running from a native DTM.
The real answer is that DTMNodeProxy probably should implement
getElementsByTagName; we left it out only because we were in a hurry
(sigh). I'd suggest posting this as an enhancement request in Bugzilla to
remind us to come back and close that gap.
