Subject: Using saxon with cocoon 2.1 - msg#00158

Previous Message by Date: click to view message preview

Unexpected behavior of intersect when variables are introduced

Consider the following xml: <div> <br/> <b>Hello</b> I am a test case to see if intersection is broken.<b>I hope it is not!</b> <br/> <b>Please</b> don't be broken because I <b> need</b> you. <br/> </div> When transformed by the following stylesheet the output is expected: <xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes"/> <xsl:template match="div"> <xsl:for-each select="br[following-sibling::node()]"> <p class="seq1"> <xsl:copy-of select="following-sibling::node()"/> </p> <p class="seq2"> <xsl:copy-of select="following-sibling::br[1]/preceding-sibling::node()"/> </p> <p class="intersect"> <xsl:copy-of select="following-sibling::node() intersect following-sibling::br[1]/preceding-sibling::node()"/> </p> </xsl:for-each> </xsl:template> </xsl:stylesheet> Output: <?xml version="1.0" encoding="UTF-8"?> <p class="seq1"> <b>Hello</b> I am a test case to see if intersection is broken.<b>I hope it is not!</b> <br/> <b>Please</b> don't be broken because I <b> need</b> you. <br/> </p> <p class="seq2"> <br/> <b>Hello</b> I am a test case to see if intersection is broken.<b>I hope it is not!</b> </p> <p class="intersect"> <b>Hello</b> I am a test case to see if intersection is broken.<b>I hope it is not!</b> </p> <p class="seq1"> <b>Please</b> don't be broken because I <b> need</b> you. <br/> </p> <p class="seq2"> <br/> <b>Hello</b> I am a test case to see if intersection is broken.<b>I hope it is not!</b> <br/> <b>Please</b> don't be broken because I <b> need</b> you. </p> <p class="intersect"> <b>Please</b> don't be broken because I <b> need</b> you. </p> However, when variables are introduced the behavior changes: xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes"/> <xsl:strip-space elements="*"/> <xsl:template match="div"> <xsl:for-each select="br[following-sibling::node()]"> <xsl:variable name="seq1" select="following-sibling::node()" as="node()*"/> <xsl:variable name="seq2" select="following-sibling::br[1]/preceding-sibling::node()" as="node()*"/> <xsl:variable name="intersect" select="$seq1 intersect $seq2" as="node()*"/> <p class="seq1"> <xsl:copy-of select="$seq1"/> </p> <p class="seq2"> <xsl:copy-of select="$seq2"/> </p> <p class="intersect"> <xsl:copy-of select="$intersect"/> </p> </xsl:for-each> </xsl:template> </xsl:stylesheet> Output: <p class="seq1"> <b>Hello</b> I am a test case to see if intersection is broken.<b>I hope it is not!</b> <br/> <b>Please</b> don't be broken because I <b> need</b> you. <br/> </p> <p class="seq2"> <b>I hope it is not!</b> I am a test case to see if intersection is broken.<b>Hello</b> <br/> </p> <p class="intersect"> <b>I hope it is not!</b> </p> <p class="seq1"> <b>Please</b> don't be broken because I <b> need</b> you. <br/> </p> <p class="seq2"> you. <b> need</b> don't be broken because I <b>Please</b> <br/> <b>I hope it is not!</b> I am a test case to see if intersection is broken.<b>Hello</b> <br/> </p> <p class="intersect"> you. </p> Is this my misunderstanding of the way sequence variables work or a Saxon bug? -Sal (who one day will find XSLT 2.0 intuitive) Mangano ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com

Next Message by Date: click to view message preview

fillbuf Internal Error

Some XML files in my possession are causing a fillbuf Internal Error when validated either with ‘Saxon7.jar’ or with ‘Saxon8.jar’.  The accompanying message list follows:   Exception in thread “main” java.lang.InternalError: fillbuf   at org.apache.crimson.parser.InputEntity.parsedContent(Unknown Source)   at org.apache.crimson.parser.Parser2.content(Unknown Source)   at org.apache.crimson.parser.Parser2.maybeElement(Unknown Source)   at org.apache.crimson.parser.Parser2.content(Unknown Source)   at org.apache.crimson.parser.Parser2.maybeElement(Unknown Source)   at org.apache.crimson.parser.Parser2.parseInternal(Unknown Source)   at org.apache.crimson.parser.Parser2.parse(Unknown Source)   at org.apache.crimson.parser.XMLReaderImpl.parse(Unknown Source)   at net.sf.saxon.event.Sender.sendSAXSource(Sender.java:185)   at net.sf.saxon.event.Sender.send(Sender.java:74)   at net.sf.saxon.Controller.transform(Controller.java:1343)   at net.sf.saxon.Transform.processFile(Transform.java:733)   at net.sf.saxon.Transform.doMain(Transform.java:437)   at net.sf.saxon.Transform.main(Transform.java:66)   Any suggestions are appreciated.   Thanks, Bill  

Previous Message by Thread: click to view message preview

Unexpected behavior of intersect when variables are introduced

Consider the following xml: <div> <br/> <b>Hello</b> I am a test case to see if intersection is broken.<b>I hope it is not!</b> <br/> <b>Please</b> don't be broken because I <b> need</b> you. <br/> </div> When transformed by the following stylesheet the output is expected: <xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes"/> <xsl:template match="div"> <xsl:for-each select="br[following-sibling::node()]"> <p class="seq1"> <xsl:copy-of select="following-sibling::node()"/> </p> <p class="seq2"> <xsl:copy-of select="following-sibling::br[1]/preceding-sibling::node()"/> </p> <p class="intersect"> <xsl:copy-of select="following-sibling::node() intersect following-sibling::br[1]/preceding-sibling::node()"/> </p> </xsl:for-each> </xsl:template> </xsl:stylesheet> Output: <?xml version="1.0" encoding="UTF-8"?> <p class="seq1"> <b>Hello</b> I am a test case to see if intersection is broken.<b>I hope it is not!</b> <br/> <b>Please</b> don't be broken because I <b> need</b> you. <br/> </p> <p class="seq2"> <br/> <b>Hello</b> I am a test case to see if intersection is broken.<b>I hope it is not!</b> </p> <p class="intersect"> <b>Hello</b> I am a test case to see if intersection is broken.<b>I hope it is not!</b> </p> <p class="seq1"> <b>Please</b> don't be broken because I <b> need</b> you. <br/> </p> <p class="seq2"> <br/> <b>Hello</b> I am a test case to see if intersection is broken.<b>I hope it is not!</b> <br/> <b>Please</b> don't be broken because I <b> need</b> you. </p> <p class="intersect"> <b>Please</b> don't be broken because I <b> need</b> you. </p> However, when variables are introduced the behavior changes: xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes"/> <xsl:strip-space elements="*"/> <xsl:template match="div"> <xsl:for-each select="br[following-sibling::node()]"> <xsl:variable name="seq1" select="following-sibling::node()" as="node()*"/> <xsl:variable name="seq2" select="following-sibling::br[1]/preceding-sibling::node()" as="node()*"/> <xsl:variable name="intersect" select="$seq1 intersect $seq2" as="node()*"/> <p class="seq1"> <xsl:copy-of select="$seq1"/> </p> <p class="seq2"> <xsl:copy-of select="$seq2"/> </p> <p class="intersect"> <xsl:copy-of select="$intersect"/> </p> </xsl:for-each> </xsl:template> </xsl:stylesheet> Output: <p class="seq1"> <b>Hello</b> I am a test case to see if intersection is broken.<b>I hope it is not!</b> <br/> <b>Please</b> don't be broken because I <b> need</b> you. <br/> </p> <p class="seq2"> <b>I hope it is not!</b> I am a test case to see if intersection is broken.<b>Hello</b> <br/> </p> <p class="intersect"> <b>I hope it is not!</b> </p> <p class="seq1"> <b>Please</b> don't be broken because I <b> need</b> you. <br/> </p> <p class="seq2"> you. <b> need</b> don't be broken because I <b>Please</b> <br/> <b>I hope it is not!</b> I am a test case to see if intersection is broken.<b>Hello</b> <br/> </p> <p class="intersect"> you. </p> Is this my misunderstanding of the way sequence variables work or a Saxon bug? -Sal (who one day will find XSLT 2.0 intuitive) Mangano ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com

Next Message by Thread: click to view message preview

RE: Using saxon with cocoon 2.1

I'm afraid I can't help you here. I understood at one time that Cocoon had a fairly intimate relationship with Xalan, for example it implemented its own extension functions and instructions. I know at one stage they were trying to get it to work with Saxon as an alternative, but I don't know what actually happened. Michael Kay > -----Original Message----- > From: saxon-help-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx > [mailto:saxon-help-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx] > On Behalf Of > Colin Paul Adams > Sent: 23 June 2004 16:55 > To: saxon-help-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx > Subject: [saxon] Using saxon with cocoon 2.1 > > Anyone know how to use saxon8 with cocoon (preferably as the default > transformer)? > I'm not getting any replies on the cocoon users list, the > documentation seems unhelpful, and my guesses at what to do have not > met with any success. > -- > Colin Paul Adams > Preston Lancashire > > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > digital self defense, top technical experts, no vendor pitches, > unmatched networking opportunities. Visit www.blackhat.com > _______________________________________________ > saxon-help mailing list > saxon-help-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx > https://lists.sourceforge.net/lists/listinfo/saxon-help > ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com