eclipse-ee4j / eclipse-ee4j/jersey

Add ability to disable DefaultJacksonJaxbJsonProvider

Open
#5,696 1 comment 0 reactions 0 assignees View on GitHub
NativeImage
Dominant language
Java
Stars
730
Forks
382
PR merge metrics
No merged PRs in 30d

Description

Currently JAXB provider is always registered unless Jackson's JAXB provider is already registered.

`
if (!config.isRegistered(JacksonJaxbJsonProvider.class)) {

if (registerExceptionMappers) {
// add the default Jackson exception mappers
context.register(JsonParseExceptionMapper.class);
context.register(JsonMappingExceptionMapper.class);
}

if (EntityFilteringFeature.enabled(config)) {
context.register(JacksonFilteringFeature.class);
context.register(FilteringJacksonJaxbJsonProvider.class, MessageBodyReader.class, MessageBodyWriter.class);
} else {
context.register(DefaultJacksonJaxbJsonProvider.class, MessageBodyReader.class, MessageBodyWriter.class);
}
}
`

This behaviour should be configurable so that DefaultJacksonJaxbJsonProvider does not need to be present in native Graal images.

Contributor guide

Open the contributing guide

Research direction

Start by locating the registration block containing DefaultJacksonJaxbJsonProvider and inspect how existing configuration controls provider registration. Define a configuration option that prevents the default provider from being registered, then verify that the provider is absent when disabled while existing registration behavior remains unchanged.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api, backend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.