-
Notifications
You must be signed in to change notification settings - Fork 356
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Make JacksonFeature configurable #5052
Milestone
Comments
This was referenced Jun 14, 2022
Closed
1 task
This was referenced Jun 18, 2022
This was referenced Dec 7, 2022
Closed
1 task
This was referenced Jan 6, 2023
Merged
This was referenced Feb 11, 2023
Closed
1 task
This was referenced May 11, 2023
This was referenced Jun 1, 2023
This was referenced Jun 4, 2023
This was referenced Jun 15, 2023
This was referenced Jul 6, 2023
This was referenced Aug 28, 2023
This was referenced Jan 16, 2024
1 task
This was referenced Apr 13, 2024
Closed
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
At present time there is no any possibility define witch modules would be registered in DefaultJacksonJaxbJsonProvider.
Current implementation of DefaultJacksonJaxbJsonProvider imports all modules(except JaxbAnnotationModule) founded in classpath. That leads to problem with unwanted modules would be registered. In example, we have jetty + jersey web server and we adding kafka to our application. Kafka has runtime dependencies to Jdk8 and Skala modules. Skala has jackson version check and any other modules can has it too. Its can create situation when auto registered 2 modules has non-overlapping version range check,wich cant be fixed by simple change jackson version.
My proposal to make registered modules in DefaultJacksonJaxbJsonProvider more configurable.
It can be achieved by
The text was updated successfully, but these errors were encountered: