Saxon

With ContentHandler being some kind of SAX interface I was wondering whether I need the
toString() call doing some serialization to a string and then the string parsing by
Saxon's DocumentBuilder or whether perhaps s9api or JAXP would allow Saxon to use that
ContentHandler as an input.

I think I do something like this in my Invisible XML implementation by
getting a BuildingContentHandler from
DocumentBuilder.newBuildingContentHandler(), but it might not be exactly
the same as what you’re trying to do.

Be seeing you,
norm

--
Norm Tovey-Walsh
Saxonica

With JAXP, you should be able to supply a TransformerHandler as the ContentHandler that the tika parser writes to, where the TransformerHandler is built from the Templates object representing the compiled stylesheet.

I don't think there's direct equivalent in s9api.

As Norm says, you can send the tika output to a ContentHandler obtained using DocumentBuilder.newBuildingContentHandler, which will build an XdmNode which you can then supply as input to the transformation. Fine unless you want to use streaming, or things like xsl:strip-space.

I can also think of a slightly convoluted approach: the XsltTransformer is a Destination, you can get that Destination as a Receiver by calling its getReceiver() method, then set this as the Receiver in a ReceivingContentHandler, and have tika write to the ReceivingContentHandler. But this seems to involve fiddling about with PipelineConfiguration's, so it's not very clean. It would be easy to clean it up with an XsltTransformer.asContentHandler() method.

Thanks a lot, ditching Tika's ToXMLContentHandler and using Saxon's BuildingContentHandler directly as the handler to the Tika parser works fine (and even avoids some hickup/bug that ToXMLContentHandler seems to have with RTF and hyperlinks).