Community Admin
- Login: admin
- Email: support@saxonica.com
- Registered on: 2012-03-22
- Last connection: 2024-11-15
Issues
open | closed | Total | |
---|---|---|---|
Assigned issues | 0 | 4 | 4 |
Reported issues | 0 | 2 | 2 |
Projects
Project | Roles | Registered on |
---|---|---|
Saxon | Manager, Developer, Reporter | 2012-03-22 |
Saxon-CE | Manager | 2012-03-23 |
Activity
2023-01-13
-
Closing this bug issue. Support #5644: Saxon-EE maven artefactsHi,
I've been reading your blog post: https://dev.saxonica.com/blog/norm/2020/10/29-maven.html on using your public (I understand it's experimental) repository for using Saxon-EE with maven. I'm having trouble using the 9.9.1 version ... -
Closing this bug issue as it has been applied to the XML Resolver 4.5.0 as mentioned in the comment #6. Bug #5635 (Closed): I cannot disable the catalog resolver disk cache and avoid it creating the cache folder and filesAny time a new transformer is created, I get a bunch of files created here:
C:/Users/radu_coravu/.xmlresolver.org/cache/
I've already set up the code to disable the cache:
```
ResourceResolver rsrcResolver = config.getResourceR... -
Bug issue fix applied in the Saxon 12.0 Major Release.
Leaving this bug marked as Resolved until fix applied Bug #5763: Failure in saxon:new-attribute() - A LazySequence can only be read once. (PEJ qt3extra XP31 test fails)```
Testing name($result) = 'a'
Testing string($result) = ''
-s:saxon-new-attribute -t:new-attribute-02
A LazySequence can only be read once
java.lang.IllegalStateException: A LazySequence can only be read once
at net.sf.saxon.om.... -
Bug issue fix applied in the Saxon 12.0 Major Release.
Leaving this bug marked as Resolved until fix applied Bug #5766: xsl:evaluate, duplicated params in @with-params and child::xsl:with-param - test case evaluate-018dThis test is passing on SaxonJ 12 and failing on SaxonCS 12.
The test expects a type error, which is not being reported in SaxonCS.
I think the test is questionable. It supplies parameters to xsl:evaluate both using the @with-param... -
Bug issue fix applied in the Saxon 12.0 Major Release.
Leaving this bug marked as Resolved until fix applied Bug #5786: Stack overflow in ExpressionTool.expressionSize()A stack overflow (infinite recursion) occurs in ExpressionTool.expressionSize() if a function A contains as a subexpression a reference to a function B which itself contains a call on A. Example:
```
xquery version "3.1";
module nam... -
Bug issue fix applied in the Saxon 12.0 Major Release.
Leaving this bug marked as Resolved until fix applied Bug #5798: Test case package-101 fails with -export:on
Intermittent `NullPointerException` when executing a two-package stylesheeet that has been reloaded from a SEF file.
In the XSLT3 test suite:
```
-s:package -t:package-101
Exported package to /Users/mike/w3c/qt3t/saxon/export/pac... -
Bug issue fix applied in the Saxon 12.0 Major Release.
Leaving this bug marked as Resolved until fix applied Bug #5800: Saxon-HE:9.5.5 and higher causes NullpointerException in GatherUsePackageDeclaration method when using xsl:include and applying custom URIResolverSaxon-HE:9.5.5 and higher causes NullpointerException in GatherUsePackageDeclaration method when using xsl:include and applying custom URIResolver
Hello, first of all I would like to thank you for the great work your team is doing.
... -
Bug issue fix applied in the Saxon 12.0 Major Release.
Leaving this bug marked as Resolved until fix applied Bug #5803: XPathExampleSA schema-aware sample application is failingThis sample application is failing on the 12.x branch, but the erroneous code is also present in 11.x and earlier releases.
The sample uses the JAXP XPath API, but with schema-aware processing.
The extension function `ToCentimetres... -
Bug issue fix applied in the Saxon 12.0 Major Release.
Leaving this bug marked as Resolved until fix applied Bug #5754: SXST0060 Component cannot be streamed, although it is guaranteed streamableSee https://saxonica.plan.io/boards/3/topics/9150
Created XSLT3 test case `si-value-of-102`. -
Bug issue fix applied in the Saxon 12.0 Major Release.
Leaving this bug marked as Resolved until fix applied Bug #5756: SaplingElement has incorrect NamespaceMap, resulting in spurious `xmlns=""`When a `SaplingElement` is created, with a no-namespace element name, it is given a `NamespaceMap` containing the namespace binding `xmlns=""`. As the documentation for class `NamespaceMap` makes clear, the map should never contain any ...
Also available in: Atom