Skip to content

Fixed XMLParsingException in case of empty XML elements#1918

Merged
copierrj merged 1 commit intodeegree:mainfrom
lat-lon:fix/handleEmptyOrNullValues-XPLANBOX-4432
Jan 28, 2026
Merged

Fixed XMLParsingException in case of empty XML elements#1918
copierrj merged 1 commit intodeegree:mainfrom
lat-lon:fix/handleEmptyOrNullValues-XPLANBOX-4432

Conversation

@lgoltz
Copy link
Copy Markdown
Contributor

@lgoltz lgoltz commented Jan 12, 2026

Currently an XMLParsingException is thrown if an non-string value element is empty. E.g.:

<nummer></nummer>

Exception: org.deegree.commons.xml.XMLParsingException: Error in XML document (line: 106,column: 7, character offset: 5327): Property '{http://www.exampl.org/xplangml/6/0}nummer' is not valid: Zero length BigInteger

Declaration of the element:

<element default="0" name="nummer" type="integer">

The GML document is valid according the application schema.

@lgoltz lgoltz added the bug error issue and bug (fix) label Jan 12, 2026
@lgoltz lgoltz added this to the 3.6.6 milestone Jan 12, 2026
@dstenger
Copy link
Copy Markdown
Contributor

It tested it and a document including <nummer></nummer> and the schema declares <element default="0" name="nummer" type="integer"> can now be parsed by deegree.

@copierrj copierrj merged commit 831f2d0 into deegree:main Jan 28, 2026
1 check passed
@tfr42 tfr42 deleted the fix/handleEmptyOrNullValues-XPLANBOX-4432 branch January 28, 2026 17:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug error issue and bug (fix)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants