Hi, Nils.
Nils Kaiser <[EMAIL PROTECTED]> wrote on 2006-05-03 12:30:44 PM:
> BTW, I use the extension to access external content because implementing
> an URIResolver did not work for me. So I return my content as a w3c DOM.
> Would be using an URIResolver faster (as I may be able to return the
> content as SAX stream)?
Internally, XSLTC will traverse a DOM tree and generate SAX events to populate a DTM representation of the input, so going to the trouble of constructing a DOM would probably be more costly than using a URIResolver whose resolve method returns a SAXSource.
> Can I also return the content as a DTM or any other internal XSLTC
> structure - or does this work for Xalan only?
It's possible to return a DTMAxisIterator (upcast to an Object) from a extension function in XSLTC, but doing that might be getting you deep into the internals of DTM. If you have any concerns about the potential for future incompatibilities, I would suggest that you not do something like that.
Thanks,
Henry
------------------------------------------------------------------
Henry Zongaro Xalan development
IBM SWS Toronto Lab T/L 969-6044; Phone +1 905 413-6044
mailto:[EMAIL PROTECTED]
- Registering an extension programmatically (not from xsl file... Nils Kaiser
- Re: Registering an extension programmatically (not from... Nils Kaiser
- Re: Registering an extension programmatically (not ... Nils Kaiser
- Re: Registering an extension programmatically (... Henry Zongaro
- Re: Registering an extension programmatical... Nils Kaiser
- Re: Registering an extension programma... Henry Zongaro
