messages from external Saxon

Here should go questions about transforming XML with XSLT and FOP.
Patrik
Posts: 231
Joined: Thu Nov 28, 2013 9:32 am
Location: Hamburg/Germany
Contact:

messages from external Saxon

Post by Patrik » Tue Mar 20, 2018 10:03 am

Hi,

with oXygen 18.1 I configured SaxonHE-9.8.0.10 as custom transformer. And within my xslt I use xsl:message to write some debugging information.

It seems that oXygen filters the messages to remove duplicated lines. So for instance with this template

Code: Select all

            <xsl:template match="/">
<xsl:for-each select="2 to 5">
<xsl:message>A {xs:integer(. div 2)}</xsl:message>
<xsl:message>B {.}</xsl:message>
</xsl:for-each>
</xsl:template>
The output is

Code: Select all

A 1
B 2
B 3
A 2
B 4
B 5
So there are missing two lines starting with "A". Running Saxon from the command line does display all the messages to I would expect this to be an issue witrh oXygen!?

Thanks and regards,
Patrik

alex_jitianu
Posts: 697
Joined: Wed Nov 16, 2005 11:11 am

Re: messages from external Saxon

Post by alex_jitianu » Tue Mar 20, 2018 4:57 pm

Hi Patrik,

I managed to reproduce this behavior myself and I've recorded an issue to fix it. Some time ago we created an extension point for contributing XSLT engines (Java-based API). If this behavior is too much of a nuisance, please let me know and I will try to build such a plugin over Saxon 9.8.0.10, one that is compatible with Oxygen 18.1.

Best regards,
Alex

Patrik
Posts: 231
Joined: Thu Nov 28, 2013 9:32 am
Location: Hamburg/Germany
Contact:

Re: messages from external Saxon

Post by Patrik » Tue Mar 20, 2018 5:03 pm

Hi Alex,

I just found out that oXygen 20.0 includes Saxon 9.8.0.8 which supports XSLT 3.0 in HE. So I will try to switch to the new version tomorrow.
(And adding some more parameters like generate-id() to the output also works good as a workaround or now.)
Thus, there's no need for an additional plugin.

Thankgs and regards,
Patrik

Post Reply