Re: apparently running into bug 4476 with Saxon 9.9.1.7

It's related to that bug entry, but the whole area is quite complex. We've gradually been implementing the generalization of collections in XSLT 3.0 to support multiple media types, not just XML, and this has sometimes broken compatibility. In addition, as reported in that bug, we found that the approach we were using to auto-detection of content type was leading to overload in terms of the number of open I/O connections, and we had to make changes to fix that. 

I would suggest doing

configuration.registerFileExtension("fods", "application/xml");

You can also define this association in a configuration file. And in 10.x you can add

content-type=application/xml 

to the collection URI

Michael Kay
Saxonica


> On 17 Aug 2020, at 17:37, Wolfhart Totschnig <[email protected]> wrote:
> 
> Hello,
> 
> After updating to Saxon 9.9.1.7 (HE), a stylesheet that used to work fine now produces an error, namely
> 
> Type error evaluating (fn:collection(...)) in xsl:for-each/@select on line 107 column 153 of new_zettel.xsl: XPTY0019: The required item type of the first operand of '/' is node(); the supplied value xs:base64Binary [...] is an atomic value
> 
> What produces the error, apparently, is the following code:
> 
> <xsl:for-each select="collection('/home/wolfhart/Desktop/.?select=export*.fods')/office:document/office:body/office:spreadsheet/table:table/table:table-row">
> 
> It seems to me that this error is related to the following bug:
> 
> https://saxonica.plan.io/issues/4476
> 
> But, according to this page, the bug was fixed in Saxon 9.9.1.7. So I don't understand why I am getting the error.
> 
> What is the solution to this?
> 
> Thanks in advance for your help.
> 
> Wolfhart
> 
> 
> 
> 
> _______________________________________________
> saxon-help mailing list archived at http://saxon.markmail.org/
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/saxon-help