saxon-help

I just tried first the -T option, and then the -TP option with saxon
8.2 (command line).
In each case I'm, getting a message:
Exception in thread "main" java.lang.AssertionError: Incestuous relationship!
at net.sf.saxon.expr.ComputedExpression.setParentExpression(ComputedExpression.java:67)
at net.sf.saxon.style.XSLChoose.compile(XSLChoose.java:136)
at net.sf.saxon.style.StyleElement.compileSequenceConstructor(StyleElement.java:1369)
at net.sf.saxon.style.StyleElement.compileSequenceConstructor(StyleElement.java:1340)
at net.sf.saxon.style.StyleElement.compileSequenceConstructor(StyleElement.java:1340)
at net.sf.saxon.style.StyleElement.compileSequenceConstructor(StyleElement.java:1340)
at net.sf.saxon.style.StyleElement.compileSequenceConstructor(StyleElement.java:1340)
at net.sf.saxon.style.StyleElement.compileSequenceConstructor(StyleElement.java:1382)
at net.sf.saxon.style.StyleElement.compileSequenceConstructor(StyleElement.java:1382)
at net.sf.saxon.style.StyleElement.compileSequenceConstructor(StyleElement.java:1382)
at net.sf.saxon.style.StyleElement.compileSequenceConstructor(StyleElement.java:1382)
at net.sf.saxon.style.StyleElement.compileSequenceConstructor(StyleElement.java:1382)
at net.sf.saxon.style.StyleElement.compileSequenceConstructor(StyleElement.java:1382)
at net.sf.saxon.style.StyleElement.compileSequenceConstructor(StyleElement.java:1382)
at net.sf.saxon.style.StyleElement.compileSequenceConstructor(StyleElement.java:1382)
at net.sf.saxon.style.XSLTemplate.compile(XSLTemplate.java:244)
at net.sf.saxon.style.XSLStylesheet.compileStylesheet(XSLStylesheet.java:938)
at net.sf.saxon.PreparedStylesheet.setStylesheetDocument(PreparedStylesheet.java:290)
at net.sf.saxon.PreparedStylesheet.prepare(PreparedStylesheet.java:112)
at net.sf.saxon.TransformerFactoryImpl.newTemplates(TransformerFactoryImpl.java:124) at net.sf.saxon.Transform.doMain(Transform.java:440)
at net.sf.saxon.Transform.main(Transform.java:58)
--
Colin Paul Adams
Preston Lancashire

>>>>> "Dimtre" == Dimtre Novatchev <dnovatchev@...> writes:
Dimtre> Can't reproduce this. Just downloaded FXSL 1.1 for XSLT
Dimtre> 2.0 from sf.net, unzipped in an empty directory and tested
Dimtre> -- works fine.
Hm. Same here.
I had made a few changes for debugging (mostly inserting
xsl:messages).
But now when I try to put the changes back, I no longer get the
problem. So I've missed something.
Sorry Michael. If I get it again, I'll collect all the files together
and send them to you.
--
Colin Paul Adams
Preston Lancashire

>>>>> "Colin" == Colin Paul Adams <colin@...> writes:
>>>>> "Dimtre" == Dimtre Novatchev <dnovatchev@...> writes:
Dimtre> Can't reproduce this. Just downloaded FXSL 1.1 for XSLT
Dimtre> 2.0 from sf.net, unzipped in an empty directory and tested
Dimtre> -- works fine.
Colin> Hm. Same here.
No. Silly me.
I had changed by saxon shell script to use saxon 8.1.1 to get round
the problem.
When I change it back to 8.2, and unzip a clean fxsl 1.1, then I get
the problem.
Dimtre, I believe you use Windows? I use Linux, so it may be an
O/S-specific thing.
Or it may be a JVM thing - I'm using Java 1.5 here (I upgraded
specifically for Saxon 8.2)
--
Colin Paul Adams
Preston Lancashire

> Dimtre> I'm using Saxon 8.2B in Windows XP with Java 1.5 "Saxon
> Dimtre> 8.2 from Saxonica Java version 1.5.0_01 Stylesheet
>
> sounds like it's Linux-specific then.
The error message occurs when the parent pointers in the abstract syntax
tree are incorrectly set up, and as it was specific to using -T, it was
presumably an error in the way that trace instructions were stitched in to
the tree. It's very unlikely that it depends on the Java version or the OS.
Let me know if you can reproduce it under 8.2.
Michael Kay

Community

Help

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

CountryState

JavaScript is required for this form.

I agree to receive quotes, newsletters and other information from sourceforge.net and its partners regarding IT services and products. I understand that I can withdraw my consent at any time. Please refer to our Privacy Policy or Contact Us for more details