Supplied value "..." is not a valid xs:base64
Maybe useful to remark that part of its life time, the parameter is a tunnel parameter.
You can watch the working version at http://www.masereeuw.nl/tangram. I'll be happy to supply source code if that helps.
Here is an abbridged snipped of my code:
<!-- ... -->
<xsl:otherwise> <xsl:message>Don't know how to deal with figure "<xsl:value-of select="$next-figure"/>".</xsl:message> </xsl:otherwise> </xsl:choose> </xsl:template>@
#1 Updated by Debbie Lockett about 2 years ago
- Status changed from New to In Progress
- Assignee set to Debbie Lockett
- Found in version changed from Saxon-JS-beta-0.9.1.1.zip to 0.9.1
Thanks for letting us know about the bug. I have managed to obtain the source code via the link to the demo that you provided. I shall investigate.
I like the demo! We are always interested in hearing from people who are using Saxon-JS. Any other feedback you have would be most welcome.
#2 Updated by Pieter Masereeuw about 2 years ago
- Company set to Pieter Masereeuw
- Contact person set to Pieter Masereeuw
I am glad that I also copied the source files to the site then. If I
can be of any other help, please let me know. I certainly like the
Saxon-JS product; I think it will offer a good replacement for many web
applications whose source code is now overly complex.
On Mon, 2017-01-09 at 13:29 +0100, Saxonica Developer Communi;ty wrote:
#3 Updated by Debbie Lockett about 2 years ago
- Status changed from In Progress to Resolved
- Applies to branch 9.7 added
The bug arises from a cast to base64Binary when processing a 'switch' expression in Expr.js.
To fix the bug, we have suppressed the choose -> switch optimisation for target="JS" on the 9.7 branch (this had previously already been suppressed on the 9.8 branch, on 2016-11-11). So when exporting using Saxon-EE 18.104.22.168 or later, an SEF will not contain any 'switch' expressions.
The next Saxon-JS release will no longer process 'switch' expressions. Now if Saxon-JS encounters a 'switch' expression in an SEF, an error is raised which tells the user to regenerate the SEF with Saxon-EE 22.214.171.124 or later.
#4 Updated by Michael Kay about 2 years ago
A little bit of background here to explain what is going on...
When you use a choose expression like this:
Please register to edit this issue