Dear Holly, The problem was recorded [1] by Michael Kay on the Saxon issue tracking system and a patch was provided. We also noticed that the issue does not appear when a certain option is turned on in Saxon and it is safe to enable that for Saxon 8 Basic and we do that in oXygen. Well, let's get to solutions. You have to options. One is to install the Saxon patch as explained below: :Saxon patch: I compiled the changed class and in order to get that in oXygen download the patch from http://www.oxygenxml.com/update/saxon999patch.jar and then create a folder called endorsed inside the oXygen lib folder and place the above patch in that folder. Note that you will need to delete that patch manually after you will uninstall oXygen in the future. The other possibility, if you are using only Saxon B and not Saxon SA is to get the latest 9.1 build [2] from our download page http://www.oxygenxml.com/download.html and upgrade your oXygen 9.1 installation. [1] http://sourceforge.net/tracker/index.php?func=detail&aid=1855418&group_id=29872&atid=397617 [2] http://www.oxygenxml.com/build_history.html#build2007122116 Best Regards, George --------------------------------------------------------------------- George Cristian Bina - http://aboutxml.blogspot.com/ <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com George Cristian Bina wrote:
Dear Holly,
Thank you for sending the sample files to reproduce the problem. We were able to reduce that to
xml: <?xml version="1.0" encoding="UTF-8"?> <x a="type"> <y/> </x>
xsl: <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:template match="x[@a= 'something']//y[@b= 'else'] "/> </xsl:stylesheet>
We will keep you updated with how this issue evolves.
Best Regards, George --------------------------------------------------------------------- George Cristian Bina - http://aboutxml.blogspot.com/ <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com
George Cristian Bina wrote:
Dear Holly,
There was a similar issue [1] reported against Saxon 9.0.0.1 and that was fixed in 9.0.0.2. oXygen 9.1 includes the latest Saxon 9.0.0.2 so the problem should be fixed. It may be also a manifestation of the same problem that was not caught by the fix, in that case we can follow up with Michael Kay and when a fix is provided we can package that as a patch you will be able to use in oXygen.
Anyway, the way forward is as Radu suggested, provide us a sample to reproduce the issue. Alternatively you can configure the older Saxon 8.9 as an external XSLT processor in oXygen and use that instead of the built in Saxon 9 that comes with the latest oXygen.
[1] the URL below may wrap on multiple lines so you may need to reconstruct it to be able to see it in the browser http://sourceforge.net/tracker/index.php?func=detail&aid=1837263&group_id=29872&atid=397617
Best Regards, George --------------------------------------------------------------------- George Cristian Bina - http://aboutxml.blogspot.com/ <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com
Holly Hendricks wrote:
Hi Soren and colleagues, The site bug reporting interface kept trashing my attempt to report this.
9.0: XML and XSLT run fine 9.1: same transform on same files generates Saxon 9B -999 error
Can I zip up the xslt and just enough of the XML to recreate this for you? The xml is large.
Thanks, Holly Hendricks Mass. Historical Society
------------------------------------------------------------------------
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user