Open rolfl opened 13 years ago
JDOM does indeed convert the JDOM content to a SAX stream, which then in turn is passed to the Transformation engine, which then feeds the results (using another SAX stream) back to JDOM.
This is a very low-level transformation, and as a result is reliable and portable.
It is not very efficient though.
Having inspected this from a few perspectives I think that:
For the moment (JDOM2) this does not need a change to this interface to make it work with other libraries. If anyone is motivated enough they can implement a specific alternate source to get it done.
This is going to be deferred for the moment. Please mail the mailing list or comment on this issue if you have ideas, patches, complaints, etc.
If you're looking at transform, it would be nice to see whether the interface to Saxon can be improved. At present, I think Saxon is being presented with a SAXSource and SAXResult so the JDOM source tree is reconstructed as a Saxon tree. Since Saxon is able to transform JDOM input directly, this is pretty inefficient.
Using Saxon to deliver XPath 2.0 access, as an alternative to Jaxen, would also be quite feasible.
(Also note: the Javadoc for org.jdom.transform.XSLTransformer is looking very dated.)
Michael Kay Saxonica