[jdom-interest] XPath and Jaxon

Michael Kay mike at saxonica.com
Tue Sep 13 08:24:34 PDT 2011

On 13/09/2011 11:10, Rolf wrote:
> One of the reasons I have left the transforms to last is because I am 
> least familiar with them. Essentially, unfamiliar with them... :( I 
> have used transform to output DOM documents as files/strings, etc, but 
> that's it.
> For the moment my immediate goal is to 'cover' what we have, so that 
> we can have a regression baseline. I looked at the XSLTransform class 
> and figured it largely just leverages the JDOMSource and JDOMResult 
> classes. I thus have focused on those first. Testing those has been 
> quite easy by simply 'piping' the results of a JDOMSource transform 
> back in to a JDOMResult. The guts of that process is using the 
> XMLOutoutter, SAXOutputter and SAXBuilder anyway which is well covered 
> too.

Thinking about it again, perhaps the onus is on Saxon to recognize and 
optimize the case where the input is supplied as a JDOMSource or the 
output as a JDOMResult. Currently it just treats these as instances of 
the superclass (SAXSource, SAXResult).

Michael Kay

More information about the jdom-interest mailing list