Norm Tovey-Walsh
- Login: norm
- Introduction email sent: Yes
- Which product do you use?: Saxon
- Registered on: 2020-08-27
- Last connection: 2024-12-19
Issues
open | closed | Total | |
---|---|---|---|
Assigned issues | 1 | 73 | 74 |
Reported issues | 11 | 84 | 95 |
Projects
Project | Roles | Registered on |
---|---|---|
Saxon | Manager, Developer, Reporter, Subscriber | 2020-08-27 |
Non-Conformances | Manager, Developer, Reporter, Subscriber | 2020-08-27 |
Saxon-CE | Manager, Developer, Reporter, Subscriber | 2020-08-27 |
SaxonC | Manager, Developer, Reporter, Subscriber | 2020-08-27 |
SaxonJS | Manager, Developer, Reporter, Subscriber | 2020-08-27 |
SaxonMirrorHE | Manager, Developer | 2020-11-23 |
W3C QT Specifications | Manager, Developer, Reporter, Subscriber | 2020-08-27 |
Activity
2024-12-06
-
Bug #6603 (New): Importing functions from an XSLT stylesheet exposes private functionsIf you compile a stylesheet, extract the function library from the prepared stylesheet, add that library to the current configuration and then evaluate XPath expressions against it, functions marked as private in the stylesheet are acces...
2024-11-27
-
Bug #6598 (In Progress): java.lang.ArrayIndexOutOfBoundsException processing 1.0 stylesheetProcessing the XSLT 4.0 schema with the W3C's (1.0) `xsd.xsl` issues an error message then throws an exception:
```
Warning: /xs:schema/xs:defaultOpenContent not matched.
Warning: /xs:schema/xs:defaultOpenContent/xs:any not matched....
2024-11-25
-
According to the Axiom docs,
> *Preserving CDATA sections during parsing*
>
> By default, StAXUtils creates StAX parsers in coaelescing mode. In this mode, the parser will never return two character data events in sequence, while i... Bug #6596: Failure upgrading to Axiom 1.4.0 - CDATA nodesAs I said in Slack
> I was trying to chase up a maven failure in a shell script. I think org.apache.ws.commons.axiom:axiom:{version} doesn't exist. I don't know why the build doesn't fail. I think that should be org.apache.ws.commons.... -
-
-
-
> I was trying to chase up a maven failure in a shell script. I think org.apache.ws.commons.axiom:axiom:{version} doesn't exist. I don't know why the build doesn't fail. I think that should be org.apache.ws.commons....
2024-11-20
-
Complete typo on my part. I left out the word **not**.
> On further reflection, it's absolutely **not** clear to me why ../../lib/ isn't being resolved against the static base URI. I mean, what I said about the Java URI class is true,... Support #6578: FORG0002 not understood !Hello !
I'm a little bit rusty on Xslt, and I need some help !
I'm trying to compile Xslt from XSpec, and my problem comes on compiling schxslt implementation.
All source code is at https://github.com/xspec/xspec/tree/v3.1.2 and...
2024-11-19
-
On further reflection, it's absolutely clear to me why `../../lib/` isn't being resolved against the static base URI. I mean, what I said about the Java `URI` class is true, but it appears that Saxon does more than that for the latter ca... Support #6578: FORG0002 not understood !Hello !
I'm a little bit rusty on Xslt, and I need some help !
I'm trying to compile Xslt from XSpec, and my problem comes on compiling schxslt implementation.
All source code is at https://github.com/xspec/xspec/tree/v3.1.2 and...
2024-11-18
-
Here's a solution that does appear to work:
```
<xsl:variable name="sbu" select="resolve-uri('../../lib/', static-base-uri())"
static="yes"/>
<xsl:variable as="map(xs:string, item())" name="x:schematr... Support #6578: FORG0002 not understood !Hello !
I'm a little bit rusty on Xslt, and I need some help !
I'm trying to compile Xslt from XSpec, and my problem comes on compiling schxslt implementation.
All source code is at https://github.com/xspec/xspec/tree/v3.1.2 and...
Also available in: Atom