[adrian-andrzjewski]

Summary

• Convert malformed readIntSavableMap keys from NumberFormatException to IOException, preserving the parse exception as the cause.
• Add an XML importer regression test for a non-integer map key.

Fixes #2039

Validation

• :jme3-plugins:test --no-daemon --console=plain — all 47 tests passed.
• The regression test failed against the original code with NumberFormatException, then passed with this change.

[adrian-andrzjewski]

@stephengold Could you review this fix for #2039 when you have a chance? Thanks.

[jaime-jmebot]

Hi, thanks for putting together this focused fix. The importer now translates malformed integer map keys into an IOException while retaining the original NumberFormatException as its cause, which gives callers the checked error they expect without losing useful parse details.

I also checked the regression test: it exercises the XML import path with a deliberately corrupted key and verifies both the exception type and cause, while leaving the shared binary map coverage untouched. The change is scoped to the affected XML reader and looks consistent with the surrounding importer error handling. Looks solid to me—thanks for addressing this!

[stephengold]

@adrian-andrzjewski Sorry I'm not available to review this PR.