SAXON 4.0 and XSL Queries

Date:     Wed, 17 Feb 1999 09:49:57 -0000
From:     Michael.Kay@icl.com
To:       xsl-list@mulberrytech.com
Subject:  RE: CSS and XSL

> From: Ray Cromwell [mailto:ray@precipita.com]
>
> The obvious API for me is one that allows me to take advantage of
> the query portion of XSL.
[. . .]

Take a look at the new SAXON 4.0 on http://home.iclweb.com/icl2/mhkay/saxon.html. (Thanks, Ed Nixon, for the plug). It's designed to meet this kind of requirement, though currently it only supports a rather small subset of the XSL pattern syntax.

The idea in SAXON is (a) from XSL you can invoke a Java element handler for a particular element type (or of course for any match pattern), and (b) from that element handler you can call applyTemplates(selectPattern) to process the selected child nodes using their registered XSL templates or Java element handlers. In other words, you can do all the routine processing in XSL and escape to Java to process any elements that need special treatment: or of course you can do it all in XSL or all in Java.

Mike Kay

XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list

Prepared by Robin Cover for the The SGML/XML Web Page archive.

SEARCH Advanced Search ABOUT Site Map CP RSS Channel Contact Us Sponsoring CP About Our Sponsors NEWS Cover Stories Articles & Papers Press Releases CORE STANDARDS XML SGML Schemas XSL/XSLT/XPath XLink XML Query CSS SVG TECHNOLOGY REPORTS XML Applications General Apps Government Apps Academic Apps EVENTS LIBRARY Introductions FAQs Bibliography Technology and Society Semantics Tech Topics Software Related Standards Historic	SAXON 4.0 and XSL Queries Date: Wed, 17 Feb 1999 09:49:57 -0000 From: Michael.Kay@icl.com To: xsl-list@mulberrytech.com Subject: RE: CSS and XSL > From: Ray Cromwell [mailto:ray@precipita.com] > > The obvious API for me is one that allows me to take advantage of > the query portion of XSL. [. . .] Take a look at the new SAXON 4.0 on http://home.iclweb.com/icl2/mhkay/saxon.html. (Thanks, Ed Nixon, for the plug). It's designed to meet this kind of requirement, though currently it only supports a rather small subset of the XSL pattern syntax. The idea in SAXON is (a) from XSL you can invoke a Java element handler for a particular element type (or of course for any match pattern), and (b) from that element handler you can call applyTemplates(selectPattern) to process the selected child nodes using their registered XSL templates or Java element handlers. In other words, you can do all the routine processing in XSL and escape to Java to process any elements that need special treatment: or of course you can do it all in XSL or all in Java. Mike Kay XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list Prepared by Robin Cover for the The SGML/XML Web Page archive.