You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@poi.apache.org by "PJ Fanning (Jira)" <ji...@apache.org> on 2026/09/17 08:39:00 UTC

[jira] [Resolved] (XMLBEANS-675) Fix PROPERTY_QSET indexing for types with several multi-name properties

     [ https://issues.apache.org/jira/browse/XMLBEANS-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

PJ Fanning resolved XMLBEANS-675.
---------------------------------
    Resolution: Fixed

> Fix PROPERTY_QSET indexing for types with several multi-name properties
> -----------------------------------------------------------------------
>
>                 Key: XMLBEANS-675
>                 URL: https://issues.apache.org/jira/browse/XMLBEANS-675
>             Project: XMLBeans
>          Issue Type: Task
>            Reporter: PJ Fanning
>            Priority: Major
>             Fix For: 5.4.1
>
>
> https://github.com/apache/poi-xmlbeans/pull/119 raised a bug related to XMLBEANS-644
> In SchemaTypeCodePrinter.printStaticFields the index counter was declared inside the per-property loop, so it reset to zero on every iteration. Every property with more than one accepted QName (typically a substitution group head) was assigned setSetIndex(0), and the generated impl class referenced PROPERTY_QSET[0] for all of them. When a type has two or more such properties, the second and later accessors silently matched the first property's element names.
> This is a regression from the XMLBEANS-644 change (December 2023). It shipped in 5.2.1, 5.3.0, 5.4.0 and 5.4.1. Before that, the index came from a map whose size supplied the next slot, which was correct.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org