Bug #5700: too many namespaces leads to ArrayIndexOutOfBoundsException - Saxon - Saxonica Developer Community

Actions

Send by e-mail Copy link

Bug #5700

closed

too many namespaces leads to ArrayIndexOutOfBoundsException

Added by Frederic Guilbeault over 1 year ago. Updated about 1 year ago.

Status:

Closed

Priority:

Normal

Assignee:

Michael Kay

Category:

Diagnostics

Sprint/Milestone:

Start date:

2022-09-29

Due date:

% Done:

100%

Estimated time:

Legacy ID:

Applies to branch:

10, 11, trunk

Fix Committed on Branch:

10, 11, trunk

Fixed in Maintenance Release:

12.0, 11.5, 10.9

Platforms:

.NET, Java

Description

with Saxon-HE 9.9.1.8J from Saxonica

if using too many namespace definitions, then an ArrayIndexOutOfBoundsException is thrown

to reproduce:

java -jar saxon9he.jar -s:too.xml -xsl:id.xslt &> error_output

refer to attached files below:

too.xml

id.xslt

error_output

Files

Download all files

too.xml (557 KB) too.xml		Frederic Guilbeault, 2022-09-29 23:32
id.xslt (481 Bytes) id.xslt		Frederic Guilbeault, 2022-09-29 23:32
error_output (821 KB) error_output		Frederic Guilbeault, 2022-09-29 23:32

Actions

Copy link

Updated by Michael Kay over 1 year ago

Category set to Diagnostics
Assignee set to Michael Kay
Priority changed from Low to Normal

Thanks for providing the test case.

The limit for a TinyTree is 1024 namespace prefixes used in a single document. We increased the limit in Saxon 9.8, it was previously 1024 prefixes globally.

The limit is there for a good reason and I don't propose to change it. But I'll look at whether we can produce better diagnostics when the limit is exceeded.

There used to be an application (Apache Axis?) that generated XML documents with a ludicrous number of namespace bindings, but I haven't seen the problem for many years. It would be interesting to know whether this is a real requirement.

Actions

Copy link

Updated by Michael Kay over 1 year ago

Status changed from New to Resolved
Applies to branch 10, 11, trunk added
Applies to branch deleted (~~9.9~~)
Fix Committed on Branch 10, 11, trunk added
Platforms .NET, Java added

The limit is actually 2047 namespace prefixes per document.

I've patched it to fail with a slightly more informative exception.

Actions

Copy link

Updated by Frederic Guilbeault over 1 year ago

Thanks for the prompt resolution. It is aligned with your expectations. There is no justifiable requirement for using so many (thousands) of namespace bindings. Applications that do this should be redesigned. If ever there is a justifiable requirements for this, I will inform you.

The focus here is more to improve the error, indeed, so that it is more informative. Thanks again for addressing this so promptly.

Actions

Copy link