Skip to Content.
Sympa Menu

xom-interest - Re: [XOM-interest] XSLTransform setParameter

xom-interest AT lists.ibiblio.org

Subject: XOM API for Processing XML with Java

List archive

Chronological Thread  
  • From: Elliotte Harold <elharo AT metalab.unc.edu>
  • To: Michael Kay <mike AT saxonica.com>
  • Cc: 'xom-interest' <xom-interest AT lists.ibiblio.org>, 'John Cowan' <jcowan AT reutershealth.com>
  • Subject: Re: [XOM-interest] XSLTransform setParameter
  • Date: Thu, 10 Feb 2005 14:08:32 -0500

Michael Kay wrote:


If a random XSLT processor can cope with XOM nodes in its principal source
document, then it can cope with them in a secondary document supplied by
parameter. (And if it can't, then it can't). I don't see the difference.

Random XSLT processors can't cope with XOM nodes. XOM converts the nodes to SAX as it's passing them to the processor on input and then builds new nodes from SAX on output. (It's *very* useful that XSL Transformations, despite the name, never actually changes the input data. It always constructs a completely new tree.)

What would Saxon do if a SAXSource were passed as the value argument to Transformer's setParameter method?

What would Saxon do if a DOM Node, NodeList, or NodeIterator were passed as the argument to Transformer's setParameter method?

--
Elliotte Rusty Harold elharo AT metalab.unc.edu
XML in a Nutshell 3rd Edition Just Published!
http://www.cafeconleche.org/books/xian3/
http://www.amazon.com/exec/obidos/ISBN=0596007647/cafeaulaitA/ref=nosim




Archive powered by MHonArc 2.6.24.

Top of Page