saxon-js

SaxonJS unusable with webpack

左心房为你撑大大i 提交于 2021-02-11 13:36:28
问题 I'm running into an issue when trying to integrate SaxonJS into a larger web application using webpack . From what I can tell, webpack views SaxonJS as just another module, but SaxonJS is not structured as an AMD or CommonJS module. Instead, the Big.js (a SaxonJS dependency) hijacks the export. I believe that fixing Node.js support will also fix this issue. import * as SaxonJS from "./Saxon-JS/SaxonJS.js"; export class Transformer { public static transform(inputStr: string, sefFile: string,

SaxonJS on Node.js

一世执手 提交于 2019-12-24 10:07:52
问题 I'm trying to run an empty simple code snippet to test SaxonJS 1.1.0 on NodeJs v8.11.1 on Windows 10. require('./Saxon-JS-1.1.0/SaxonJS.js'); But I got this error : PS C:\XXX\sandbox\xsl-transformation> node main.js C:\XXX\xsl-transformation\Saxon-JS-1.1.0\SaxonJS.js:17136 setPlatform(JSTestDriver.platform); ^ ReferenceError: JSTestDriver is not defined at initialize (C:\XXX\sandbox\xsl-transformation\Saxon-JS-1.1.0\SaxonJS.js:17136:25) Looking at the source code, I can see : function

Calling jQuery-UI components in XSL using Saxon-JS and its global Javascript function namespace?

為{幸葍}努か 提交于 2019-12-08 07:51:13
问题 Related to this question, you can call Javascript functions from XSL 2.0 transforms running in the browser using Saxon-JS. But I can't seem to invoke the jQuery-UI calls. My only thought is that it may be a timing issue where the jQuery selector can not find the target object's ID because Saxon-JS has yet to render it to the DOM. My simple test follows... The XML... <?xml version="1.0" encoding="UTF-8"?> <data> <date month="7" day="17" year="2017"/> </data> The XSL... <?xml version="1.0"

Calling jQuery-UI components in XSL using Saxon-JS and its global Javascript function namespace?

六眼飞鱼酱① 提交于 2019-12-07 00:31:34
Related to this question, you can call Javascript functions from XSL 2.0 transforms running in the browser using Saxon-JS. But I can't seem to invoke the jQuery-UI calls. My only thought is that it may be a timing issue where the jQuery selector can not find the target object's ID because Saxon-JS has yet to render it to the DOM. My simple test follows... The XML... <?xml version="1.0" encoding="UTF-8"?> <data> <date month="7" day="17" year="2017"/> </data> The XSL... <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet xmlns:js="http://saxonica.com/ns/globalJS" xmlns:xsl="http://www.w3.org