Saxon

When transformation output is sent to a SAXResult (or any kind of destination other than a serializer), there is no information available about the locations in the stylesheet that generated each output event. This has several consequences: it can lead to poor diagnostics when errors are detected within the output pipeline (e.g. output validation errors, or writing attributes when there is no open start tag), it prevents debugging tools doing back-mapping from the result document to the stylesheet, and it may mean that the base URI on output documents is not correctly set.

A patch is being applied to the 9.6 and 9.7 branches, in module net.sf.saxon.s9api.XsltTransformer.

The problem was present in earlier releases but only affected applications using the s9api interface; in 9.6 the problem is more noticeable because the JAXP transformer API is now layered on top of s9api.