-
-
Notifications
You must be signed in to change notification settings - Fork 34
Jackson JSONP Provider #111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
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 |
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 |
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 |
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 |
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 |
It looks like the main action needed here is to implement a "bridge" |
Hi @sigpwned |
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. |
V2 has been canceled because of lack of funding. |
3/6 dependent libraries use jackson
1/6 gson
The text was updated successfully, but these errors were encountered: