Add disableJsonB option to NOT use avaje-jsonb in code generation eve… #574
Conversation
This file contains 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
…n if it's in the classpath
SentryMan
approved these changes
Mar 10, 2025
|
Had someone creating a Nima rest api, it was using JAX-B generated classes for request/response types ... and those used java.util.Calendar [and also no setters for the collections]. So there wasn't a relatively quick/easy way to turn off the use of avaje-jsonb in the generated code and just use Jackson [apart from removing avaje-jsonb entirely from the classpath]. So this is there to support that type of case, where someone hits some issue and just wants to "downgrade" to using Jackson [perhaps temporarily until any issue with avaje-jsonb is sorted]. |
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.
…n if it's in the classpath