Hi,

I'll throw in my thanks to Jirka for smoothing the way and again to oXygenXML team for the advanced features. iXML is awesome.

Best regards, Wendell


On Wed, Oct 14, 2026 at 3:24 AM Oxygen XML Editor Support (Teo Timplaru) <support@oxygenxml.com> wrote:
Hi Jirka,

Thanks for the detailed report.
This turned out to be a real bug on our side, in the Saxon 13.0 XSLT & XQuery processor add-on itself, not something wrong with how you set it up.

Root cause: the add-on builds its Saxon `Configuration` directly, and then wraps that raw `Configuration` straight into a `TransformerFactory`, without ever constructing an s9api `Processor` around it.
That's fine for ordinary XSLT/XQuery transformations - they never touch the `Configuration`'s back-reference to its owning `Processor`.
But Saxon 13's new `ixml()` function does need that reference internally (it calls `.newDocumentBuilder()` on it to build its result tree), and since it was never set, you get exactly the NullPointerException you ran into.

This has likely been true of this add-on's architecture for a while.
It just never mattered until a function that actually needs that reference (`ixml()`) came along in Saxon 13.

We'll get this fixed in the add-on on our end.
In the meantime, there isn't a configuration change or workaround you can apply yourself - this needs a code fix in the add-on's own transformer wiring.
We'll let you know once an updated build is available.

Thanks again for the clear, easy-to-follow repro.
It made tracking this down quick.

Best regards,
Teo



On 10/13/2026 12:18 PM, Jirka Kosek wrote:
Hi,

I'm trying to use Saxon 13 plugin together with a new invisible-xml() functionality introduced in XSLT 4.0.

I've been able to missing Java libraries (coffeefilter, coffeegrinder) into plugin's lib folder.

Normal transformation now works fine. But when I try to use ixml parser I'm getting the following error message:

Cannot invoke "net.sf.saxon.s9api.Processor.newDocumentBuilder()" because "this.processor" is null

I suppose that there is some configuration glitch I'm not able to figure out.

Many thanks in advance,

                Jirka


_______________________________________________
oXygen-user mailing list -- oxygen-user@oxygenxml.com
To unsubscribe send an email to oxygen-user-leave@oxygenxml.com


_______________________________________________
oXygen-user mailing list -- oxygen-user@oxygenxml.com
To unsubscribe send an email to oxygen-user-leave@oxygenxml.com


--
...Wendell Piez... ...wendellpiez.com...
...pellucidliterature.org... ...raventracks.org...
... xproc.zone... ...github.com/wendellpiez...