Saxon XSLT and XQuery Processor

Saxon 6.5.5 fails to process an error on XPath functions that are given a
wrong number of arguments, e.g. :

<xsl:template match="link[starts-with('http://')]"/>

<xsl:template match="link[contains('http://')]"/>

Etc.

Instead, it dies with a "XSLT Processor Internal Error:
java.lang.NullPointerException".
This is annoying when the stylesheet is long since no location is given.

Notes:
. dev.saxonica.com seems to be presently down.
. Saxon 6.5.5 is still the default XSLT processor in oXygen XML 14.

-- Laurent CAPRANI
   Montréal

[saxon] Saxon 6.5.5 NullPointerException on wrong number of arguments From: LAURENT CAPRANI <laurent.caprani@be...> - 2012-09-24 00:15 Saxon 6.5.5 fails to process an error on XPath functions that are given a wrong number of arguments, e.g. : <xsl:template match="link[starts-with('http://')]"/> <xsl:template match="link[contains('http://')]"/> Etc. Instead, it dies with a "XSLT Processor Internal Error: java.lang.NullPointerException". This is annoying when the stylesheet is long since no location is given. Notes: . dev.saxonica.com seems to be presently down. . Saxon 6.5.5 is still the default XSLT processor in oXygen XML 14. -- Laurent CAPRANI Montréal

Re: [saxon] Saxon 6.5.5 NullPointerException on wrong number of arguments From: Andrew Welch <andrew.welch@gm...> - 2012-09-24 09:17 On 23 September 2012 19:10, LAURENT CAPRANI <laurent.caprani@...> wrote: > Saxon 6.5.5 fails to process an error on XPath functions that are given a > wrong number of arguments, e.g. : > > <xsl:template match="link[starts-with('http://')]"/> > > <xsl:template match="link[contains('http://')]"/> > > Etc. > > Instead, it dies with a "XSLT Processor Internal Error: > java.lang.NullPointerException". > This is annoying when the stylesheet is long since no location is given. I can't reproduce this using Oxygen 13.2 and Saxon 6.5.5, can you post a small complete runnable example that I can run to see the problem. -- Andrew Welch http://andrewjwelch.com

Re: [saxon] Saxon 6.5.5 NullPointerException on wrong number of arguments From: George Cristian Bina <george@ox...> - 2012-09-24 09:46 Hi Laurent, oXygen uses Saxon 6.5 for XSLT 1.0 because that is an XSLT 1.0 engine and Saxon 9 may perform differently on an XSLT 1.0 stylesheet than Saxon 6.5 - being an XSLT 2+ engine, Saxon 9 will run XSLT 1.0 in compatibility mode. Here it is the complete stack trace, reproducing the issue outside oXygen, from the command line: g:test george$ java -jar ../workspace/eXml/lib/saxon.jar test.xml test.xsl java.lang.NullPointerException at com.icl.saxon.functions.StartsWith.getDependencies(StartsWith.java:74) at com.icl.saxon.expr.Expression.usesCurrent(Expression.java:193) at com.icl.saxon.expr.ExpressionParser.parseFilters(ExpressionParser.java:976) at com.icl.saxon.expr.ExpressionParser.patternStep(ExpressionParser.java:918) at com.icl.saxon.expr.ExpressionParser.parsePathPattern(ExpressionParser.java:802) at com.icl.saxon.expr.ExpressionParser.parseUnionPattern(ExpressionParser.java:736) at com.icl.saxon.expr.ExpressionParser.parsePattern(ExpressionParser.java:75) at com.icl.saxon.pattern.Pattern.make(Pattern.java:29) at com.icl.saxon.style.StyleElement.makePattern(StyleElement.java:249) at com.icl.saxon.style.XSLTemplate.prepareAttributes(XSLTemplate.java:125) at com.icl.saxon.style.StyleElement.processAttributes(StyleElement.java:176) at com.icl.saxon.style.StyleElement.processAllAttributes(StyleElement.java:156) at com.icl.saxon.style.XSLStyleSheet.processAllAttributes(XSLStyleSheet.java:504) at com.icl.saxon.style.XSLStyleSheet.preprocess(XSLStyleSheet.java:348) at com.icl.saxon.PreparedStyleSheet.setStyleSheetDocument(PreparedStyleSheet.java:174) at com.icl.saxon.PreparedStyleSheet.prepare(PreparedStyleSheet.java:131) at com.icl.saxon.TransformerFactoryImpl.newTemplates(TransformerFactoryImpl.java:120) at com.icl.saxon.StyleSheet.doMain(StyleSheet.java:319) at com.icl.saxon.StyleSheet.main(StyleSheet.java:47) Best Regards, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 9/23/12 9:10 PM, LAURENT CAPRANI wrote: > Saxon 6.5.5 fails to process an error on XPath functions that are given a > wrong number of arguments, e.g. : > > <xsl:template match="link[starts-with('http://')]"/> > > <xsl:template match="link[contains('http://')]"/> > > Etc. > > Instead, it dies with a "XSLT Processor Internal Error: > java.lang.NullPointerException". > This is annoying when the stylesheet is long since no location is given. > > Notes: > . dev.saxonica.com seems to be presently down. > . Saxon 6.5.5 is still the default XSLT processor in oXygen XML 14. > > -- Laurent CAPRANI > Montréal > > > > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > saxon-help mailing list archived at http://saxon.markmail.org/ > saxon-help@... > https://lists.sourceforge.net/lists/listinfo/saxon-help >

Re: [saxon] Saxon 6.5.5 NullPointerException on wrong number of arguments From: Radu Coravu <radu_coravu@sy...> - 2012-09-24 10:02 Hi, The bug can be reproduced with both Oxygen 13.2 and 14 if Saxon 6.5.5 is used to validate a simple stylesheet: > <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" > xmlns:xs="http://www.w3.org/2001/XMLSchema" > exclude-result-prefixes="xs" > version="1.0"> > <xsl:template match="link[starts-with('http://')]"/> > </xsl:stylesheet> The full NPE stack trace: > java.lang.NullPointerException > at com.icl.saxon.functions.StartsWith.getDependencies(StartsWith.java:74) > at com.icl.saxon.expr.Expression.usesCurrent(Expression.java:193) > at com.icl.saxon.expr.ExpressionParser.parseFilters(ExpressionParser.java:976) > at com.icl.saxon.expr.ExpressionParser.patternStep(ExpressionParser.java:918) > at com.icl.saxon.expr.ExpressionParser.parsePathPattern(ExpressionParser.java:802) > at com.icl.saxon.expr.ExpressionParser.parseUnionPattern(ExpressionParser.java:736) > at com.icl.saxon.expr.ExpressionParser.parsePattern(ExpressionParser.java:75) > at com.icl.saxon.pattern.Pattern.make(Pattern.java:29) > at com.icl.saxon.style.StyleElement.makePattern(StyleElement.java:287) > at com.icl.saxon.style.XSLTemplate.prepareAttributes(XSLTemplate.java:125) > at com.icl.saxon.style.StyleElement.processAttributes(StyleElement.java:207) > at com.icl.saxon.style.StyleElement.processAllAttributes(StyleElement.java:189) > at com.icl.saxon.style.XSLStyleSheet.processAllAttributes(XSLStyleSheet.java:504) > at com.icl.saxon.style.XSLStyleSheet.preprocess(XSLStyleSheet.java:348) > at com.icl.saxon.PreparedStyleSheet.setStyleSheetDocument(PreparedStyleSheet.java:174) > at com.icl.saxon.PreparedStyleSheet.prepare(PreparedStyleSheet.java:131) > at com.icl.saxon.TransformerFactoryImpl.newTemplates(TransformerFactoryImpl.java:120) > at com.icl.saxon.TransformerFactoryImpl.newTransformer(TransformerFactoryImpl.java:72) So Andrew, either you have the @version set to "2.0" in the XSL or you have a transformation scenario associated to the XSL which uses Saxon 9 for validation. About Laurent's remark: > Saxon 6.5.5 is still the default XSLT processor in oXygen XML 14. Yes, Saxon 6.5.5 is still considered the default XSLT 1.0 validator engine. There is a preferences page called "XML / XSLT-FO-XQuery / XSLT" where you can control this. Also, as explained above, if you set the @version attribute in the XSL to "2.0" Or if you have a transformation scenario associated to the XSL which uses Saxon 9, Saxon 9 will be used for validation. We'll try to add a patch in Oxygen in order to guard this problem. Regards, Radu Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 9/24/2012 12:17 PM, Andrew Welch wrote: > On 23 September 2012 19:10, LAURENT CAPRANI <laurent.caprani@...> wrote: >> Saxon 6.5.5 fails to process an error on XPath functions that are given a >> wrong number of arguments, e.g. : >> >> <xsl:template match="link[starts-with('http://')]"/> >> >> <xsl:template match="link[contains('http://')]"/> >> >> Etc. >> >> Instead, it dies with a "XSLT Processor Internal Error: >> java.lang.NullPointerException". >> This is annoying when the stylesheet is long since no location is given. > > I can't reproduce this using Oxygen 13.2 and Saxon 6.5.5, can you post > a small complete runnable example that I can run to see the problem. > >

Re: [saxon] Saxon 6.5.5 NullPointerException on wrong number of arguments From: Andrew Welch <andrew.welch@gm...> - 2012-09-24 10:27 >> <xsl:template match="link[starts-with('http://')]"/> > So Andrew, either you have the @version set to "2.0" in the XSL or you > have a transformation scenario associated to the XSL which uses Saxon 9 > for validation. Sorry I did: match="*:foo[starts-with('http://')]"> ...which wasn't recreating the problem exactly as it was stated. -- Andrew Welch http://andrewjwelch.com

Re: [saxon] Saxon 6.5.5 NullPointerException on wrong number of arguments From: Michael Kay <mike@sa...> - 2012-09-24 12:03 Thanks for reporting it. It's the first bug we've noted against Saxon 6.5.5 for nearly two years, and the most serious one in rather longer than that. Surprising! I will add it to the list of known bugs at http://saxon.sourceforge.net/saxon6.5.5/limitations.html but I'm afraid it's unlikely to get fixed. We haven't touched the Saxon 6 line in nearly 7 years, and 6.5.5 itself was the first release in quite a while, funded by a customer who was prepared to pay for a bug fix. Rebuilding the product at this stage would inevitably be tricky, for example it's not easy to get hold of old versions of Java to test against. Sorry about the chronic performance problems with Redmine over the weekend. The service has been stable for a few months and we thought we had resolved the issues, so we're disappointed they have reappeared. We're working on it. Michael Kay Saxonica On 23/09/2012 19:10, LAURENT CAPRANI wrote: > Saxon 6.5.5 fails to process an error on XPath functions that are given a > wrong number of arguments, e.g. : > > <xsl:template match="link[starts-with('http://')]"/> > > <xsl:template match="link[contains('http://')]"/> > > Etc. > > Instead, it dies with a "XSLT Processor Internal Error: > java.lang.NullPointerException". > This is annoying when the stylesheet is long since no location is given. > > Notes: > . dev.saxonica.com seems to be presently down. > . Saxon 6.5.5 is still the default XSLT processor in oXygen XML 14. > > -- Laurent CAPRANI > Montréal > > > > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > saxon-help mailing list archived at http://saxon.markmail.org/ > saxon-help@... > https://lists.sourceforge.net/lists/listinfo/saxon-help >

Re: [saxon] Saxon 6.5.5 NullPointerException on wrong number of arguments From: Dave Pawson <dave.pawson@gm...> - 2012-09-24 13:31 On 24 September 2012 13:03, Michael Kay <mike@...> wrote: > Thanks for reporting it. It's the first bug we've noted against Saxon > 6.5.5 for nearly two years, and the most serious one in rather longer > than that. Surprising! > > I will add it to the list of known bugs at > > http://saxon.sourceforge.net/saxon6.5.5/limitations.html > > but I'm afraid it's unlikely to get fixed. We haven't touched the Saxon > 6 line in nearly 7 years, and 6.5.5 itself was the first release in > quite a while, funded by a customer who was prepared to pay for a bug > fix. Rebuilding the product at this stage would inevitably be tricky, > for example it's not easy to get hold of old versions of Java to test > against. I think it's fair to say that xslt 1.0 is still in wide use Mike. Were you to restrict, say Saxon 6.6 to Java version x.x then I doubt you'd hear many complaints. Just a thought. regards -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. http://www.dpawson.co.uk

Re: [saxon] Saxon 6.5.5 NullPointerException on wrong number of arguments From: Michael Kay <mike@sa...> - 2012-09-24 13:50 On 24/09/2012 14:31, Dave Pawson wrote: > On 24 September 2012 13:03, Michael Kay <mike@...> wrote: >> Thanks for reporting it. It's the first bug we've noted against Saxon >> 6.5.5 for nearly two years, and the most serious one in rather longer >> than that. Surprising! >> >> I will add it to the list of known bugs at >> >> http://saxon.sourceforge.net/saxon6.5.5/limitations.html >> >> but I'm afraid it's unlikely to get fixed. We haven't touched the Saxon >> 6 line in nearly 7 years, and 6.5.5 itself was the first release in >> quite a while, funded by a customer who was prepared to pay for a bug >> fix. Rebuilding the product at this stage would inevitably be tricky, >> for example it's not easy to get hold of old versions of Java to test >> against. > I think it's fair to say that xslt 1.0 is still in wide use Mike. Sure it is. But I left it behind many years ago, and would never choose to go back. If someone paid us sufficient money, we might do a maintenance release, but we're certainly not going to do it because it's a fun way to spend our time. After all, our business thrives on encouraging people to move forward to something more productive and efficient. And this after all, like nearly all the bugs reported in the last few years, is only a secondary failure - poor diagnostics when given an incorrect stylesheet. Would you expect Microsoft to bring out a new release of VS2003 to fix such a problem? Michael Kay Saxonica

Re: [saxon] Saxon 6.5.5 NullPointerException on wrong number of arguments From: Dave Pawson <dave.pawson@gm...> - 2012-09-24 15:07 No, but then again, I used to differentiate you from M$... perhaps I was wrong. On 24 September 2012 14:50, Michael Kay <mike@...> wrote: > > On 24/09/2012 14:31, Dave Pawson wrote: >> On 24 September 2012 13:03, Michael Kay <mike@...> wrote: >>> Thanks for reporting it. It's the first bug we've noted against Saxon >>> 6.5.5 for nearly two years, and the most serious one in rather longer >>> than that. Surprising! >>> >>> I will add it to the list of known bugs at >>> >>> http://saxon.sourceforge.net/saxon6.5.5/limitations.html >>> >>> but I'm afraid it's unlikely to get fixed. We haven't touched the Saxon >>> 6 line in nearly 7 years, and 6.5.5 itself was the first release in >>> quite a while, funded by a customer who was prepared to pay for a bug >>> fix. Rebuilding the product at this stage would inevitably be tricky, >>> for example it's not easy to get hold of old versions of Java to test >>> against. >> I think it's fair to say that xslt 1.0 is still in wide use Mike. > Sure it is. But I left it behind many years ago, and would never choose > to go back. If someone paid us sufficient money, we might do a > maintenance release, but we're certainly not going to do it because it's > a fun way to spend our time. After all, our business thrives on > encouraging people to move forward to something more productive and > efficient. > > And this after all, like nearly all the bugs reported in the last few > years, is only a secondary failure - poor diagnostics when given an > incorrect stylesheet. Would you expect Microsoft to bring out a new > release of VS2003 to fix such a problem? > > Michael Kay > Saxonica > > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > saxon-help mailing list archived at http://saxon.markmail.org/ > saxon-help@... > https://lists.sourceforge.net/lists/listinfo/saxon-help -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. http://www.dpawson.co.uk

Re: [saxon] Saxon 6.5.5 NullPointerException on wrong number of arguments From: Andrew Welch <andrew.welch@gm...> - 2012-09-24 15:18 On 24 September 2012 16:07, Dave Pawson <dave.pawson@...> wrote: > No, but then again, I used to differentiate you from M$... perhaps I was wrong. It's different from the other side of the free software divide... if you are on the receiving end of requests from users to do something for nothing you would understand. -- Andrew Welch http://andrewjwelch.com

Re: [saxon] Saxon 6.5.5 NullPointerException on wrong number of arguments From: Dave Pawson <dave.pawson@gm...> - 2012-09-24 15:34 On 24 September 2012 16:18, Andrew Welch <andrew.j.welch@...> wrote: > On 24 September 2012 16:07, Dave Pawson <dave.pawson@...> wrote: >> No, but then again, I used to differentiate you from M$... perhaps I was wrong. > > It's different from the other side of the free software divide... I never have been Andrew. regards -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. http://www.dpawson.co.uk

1 message has been excluded from this view by a project administrator.