[Michael Kay <mike@sa...>]

I think the only way of doing this at the moment is to write a class that
implements XMLReader and supply this with the SAXSource.

I'd quite like to supply a complete JAXP interface for XQuery - there's
nothing in it that's absolutely XSLT-specific - but of course there are
other things on the to-do list as well.

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

> -----Original Message-----
> From: saxon-help-admin@... 
> [mailto:saxon-help-admin@...] On Behalf Of 
> Sylvain Loiseau
> Sent: 21 December 2004 19:03
> To: saxon-help@...
> Subject: [saxon] (no subject)
> 
> Hello,
> 
> I'm wondering if anyone has already written a SAX handler 
> performing XQuery
> transformation using Saxon.
> 
> More precisely I would include a xquery transformation step 
> into a pipeline
> (such as allows the TransformerHandler of JAXP for XSLT). But 
> the problem is
> that  javax.xml.transform.sax.SAXSource (which is the only 
> way I found for
> turning the SAX stream into a " DocumentInfo " required by the
> DynamicQueryContext) ask for a org.xml.sax.XMLReader, rather 
> than being a
> mere ContentHandler, which prevents me from using it.
> 
> Is there another way for turning SAX stream into a 
> DocumentInfo, where the
> class building the DocumentInfo implements only the consumer 
> interfaces ?
> 
> Best,
> Sylvain Loiseau
> 
> 
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from 
> real users.
> Discover which products truly live up to the hype. Start reading now. 
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> saxon-help mailing list
> saxon-help@...
> https://lists.sourceforge.net/lists/listinfo/saxon-help
>