use Jakarta JAXB with minimal backwards incompatibility #247
Conversation
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
|
I've just added |
|
this is a very good approach to deal with the namespace trouble, thanks. |
This was referenced Jan 16, 2022
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is an attempt to allow the Jakarta JAXB implementation to be used by adding a new
xmlunit-jakarta-jaxb-impldependency. At least it passes my rudimentary tests (I don't use either version of JAXB myself in any real project).It currently lacks documentation, something I should be able to fix the coming weekend.
jaxb-runtimeandjakarta.xml.bind-api.MarshallerIt introduces (at least) one breaking change. If you want to invoke
withMarshalleryou must explicitly cast theJaxbBuilder.see #227
/cc @michael-schnell @phbenisc @Joerg-Schoemer