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: "Michael Kay" <mike AT saxonica.com>
  • To: "'Elliotte Harold'" <elharo AT metalab.unc.edu>
  • 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 17:50:00 -0000

Saxon's getting close to doing that: in 8.3, external object models (such as
XOM) can be registered, with a class whose job is to take care of
model-dependent operations like this. It's not quite there yet, but heading
in that direction. Obviously the linking all needs to be very dynamic.

Michael Kay
http://www.saxonica.com/


> -----Original Message-----
> From: Elliotte Harold [mailto:elharo AT metalab.unc.edu]
> Sent: 10 February 2005 17:31
> To: Michael Kay
> Cc: 'John Cowan'; 'xom-interest'
> Subject: Re: [XOM-interest] XSLTransform setParameter
>
> Michael Kay wrote:
>
> > In Saxon 8.2 you can supply a XOM node wrapped in a Saxon
> NodeWrapper and it
> > should work fine.
>
> That's going to be tricky to do without dragging Saxon along for the
> ride. Saxon really can't work with any standard DOM class instead? is
> there any way Saxon could recognize if its receiving a XOM Node,
> Document, or Nodes and do the wrapping itself?
>
> --
> 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