Project

Profile

Help

Bug #4515

closed

xsl:expose names="foo:*" with undeclared prefix foo causes NullPointerException

Added by Michael Kay about 4 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Diagnostics
Sprint/Milestone:
-
Start date:
2020-04-08
Due date:
% Done:

100%

Estimated time:
Legacy ID:
Applies to branch:
10, 9.9
Fix Committed on Branch:
10, 9.9
Fixed in Maintenance Release:
Platforms:

Description

<xsl:expose names="foo:*"/>

with undeclared prefix foo causes a NullPointerException in both 9.9 and 10.0

Stack trace:

java.lang.NullPointerException
	at net.sf.saxon.pattern.NamespaceTest.hashCode(NamespaceTest.java:178)
	at net.sf.saxon.trans.ComponentTest.hashCode(ComponentTest.java:76)
	at java.util.HashMap.hash(HashMap.java:338)
	at java.util.HashMap.put(HashMap.java:611)
	at java.util.HashSet.add(HashSet.java:219)
	at net.sf.saxon.style.XSLAcceptExpose.addWildCardTest(XSLAcceptExpose.java:193)
	at net.sf.saxon.style.XSLAcceptExpose.prepareAttributes(XSLAcceptExpose.java:155)
	at net.sf.saxon.style.StyleElement.processAttributes(StyleElement.java:588)

Added test case expose-926 to XSLT 3.0 test suite.

Actions #1

Updated by Michael Kay about 4 years ago

  • Status changed from New to Resolved
  • Fix Committed on Branch 10, 9.9 added

Fixed several days ago.

Actions #2

Updated by O'Neil Delpratt almost 4 years ago

  • % Done changed from 0 to 100
  • Fixed in Maintenance Release 10.1 added

Bug fix committed in the Saxon 10.1 maintenance release.

Actions #3

Updated by O'Neil Delpratt over 3 years ago

  • Status changed from Resolved to Closed
  • Fixed in Maintenance Release 10.2, 9.9.1.8 added
  • Fixed in Maintenance Release deleted (10.1)

Bug fix applied on the Saxon 9.9.1.8 maintenance release.

Please register to edit this issue

Also available in: Atom PDF