Thanks Joe. Looks like we'll have to live with this for the time being. :-)
Wish you and every body a Merry Christmas and a Happy New Year!

Gaurav

Joseph Kesselman wrote:

On Thursday, 12/18/2003 at 12:53ZE5B, Gaurav <[EMAIL PROTECTED]> wrote:
  
On your comment that, using a DOMSource is a performance hit for XSLTC,
    
can
  
you suggest a work around?
    

Since your document is already in a DOM (or something with a DOM adapter
layers), using the DOMSource is probably the best option currently
available. The problem is that wrapping DTM's API around DOM has some
inherent efficiency problems due to the difficulty of binding numeric node
handles to DOM objects.

If your document _wasn't_ already in a DOM, your best bet would be to let
us build the model by passing us a SAXSource or StreamSource. But streaming
the DOM out and back in would make matters worse rather than better.

  
Is this limitation something that the XSLTC team is working on?
    

We're looking at repositioning DTM strictly as a back end model and
changing our document API to XDM, which should improve this situation. But
that's still Work In Progress and hasn't been folded into the main Xalan
code base yet.


  

--
email_sig Gaurav Gandhi <[EMAIL PROTECTED]>
Sun Microsystems, Inc.




Reply via email to