MID-10558 Avoid JAXB namespace imports in schema XSD#13
Open
kay1313 wants to merge 1 commit into
Open
Conversation
JAXB customization namespaces may be used in generated schema annotations, but they should not be emitted as schema imports. Skip known non-importable customization namespaces when collecting schema imports, so generated schemas no longer contain unnecessary JAXB imports that later trigger resolver errors.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes unnecessary
XmlEntityResolverImplerrors when schemas with enumeration definitions are serialized and parsed.Enum schema serialization intentionally emits JAXB customization annotations, such as
jaxb:typesafeEnumClassandjaxb:typesafeEnumMember. These annotations are valid insidexsd:annotation/xsd:appinfo, but their namespace should not be emitted as an XSD import.Before this change, the serializer generated an unnecessary import:
This made schema parsing try to resolve the Jakarta JAXB namespace as an external schema, producing log errors like:
Changes