Jackson JSONP Provider

[filip26]

3/6 dependent libraries use jackson
1/6 gson

[filip26]

FasterXML/jackson-datatypes-misc#6

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days

[sigpwned]

It looks like the main action needed here is to implement a "bridge" JsonProvider class that uses Jackson to implement JSON-P. I think that's probably a Jackson concern. It's worth proposing it on Jackson's future ideas board. I'll link back here when I have the chance to make the proposal.

[filip26]

Hi @sigpwned
having Jackson implementing JsonProvider would be great. Thanks

[edouardhue]

It sound like the Jackson project does not want to implement JSON-P. The question was raised a long time ago and the JSR was disregarded. almost ten years and several new JSRs later, Jackson still does not implement JSON-P, I believe they never will.

Jackson provides a Jakarta JSON datatype that makes it rather simple to convert a Jackson tree to a Jakarta tree.

var jacksonNode = JsonNodeFactory.instance.objectNode();
var mapper = JsonMapper.builder().addModule(new JSONPModule()).build();
var jakartaNode = mapper.convertValue(jacksonNode, JsonObject.class);

Still, it would be nice not to have to convert, and Jackson remains widely used. Some libraries (like Jersey) support several JSON providers, but this may be tedious implementing.