-
Notifications
You must be signed in to change notification settings - Fork 6
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
JSON-B implementation #19
Comments
I am not at all opposed to increasing inter-operability, but from what I remember there were some fundamental challenges in making Jackson implement JSON-B "natively". However if someone wants to try it out I have nothing against that. Forking |
News on this? |
No news here. But one thing I'll point is that what you suggest is slightly different, an easier to implement than actual JSON-B implementation: similar to how JAXB annotations are supported via extension module ( So it might make sense to create a separate issue, so outline possibility of this as a distinct thing. |
Hi, is there any news on fasterxml.jackson-databind to comply to the json-b standard yet... thus a package that handles the annotations defined in JSR-367 as mentioned by @cowtowncoder? https://jcp.org/en/jsr/detail?id=367 |
@xtroce Volunteers welcome! I am not aware of anyone tackling this yet. Unfortunately I do not have time myself (or specific use case) to do that, but adding support for annotations could be a fun project for someone; for example for a hackathon. Would have been something for Hacktoberfest participants. |
I'm willing to make a Jackson JSON Binding that is TCK compliant. This is the project: https://github.com/devcon5io/jackson-jsonb-provider I actually don't know if I can just fork it and can add the fixes or if I need to reimplement it in a new package. After that, I don't know if the project could be part of the FasterXML repo. But I guess this is a start :) |
Looks like it would need a rewrite to actually use the JSONP. So I'll start by updating the project https://github.com/pgelinas/jackson-javax-json to the Jakarta namespace and hope that it can pass the TCK. |
@Thihup yes, the close coupling of JSON-B to underlying JSON-P which makes it not possible for main jackson-databind to directly implement JSON-B. It would, however, be possible to implement JSON-P on jackson streaming (jackson-core), which I think is what you are planning. |
That project implemented partially the JSON-P 1.0, so it misses the new APIs added in 1.1. I still need to learn what is JsonPointer to be able to implement that stuff correctly. There is another problem that I'm struggling to know the best way to fix: Running the TCK with my fork:
|
Existence of TCK is nice -- are those actually freely available these days? Either way, good way to compare. |
Yes, Oracle donated all Java EE stuff to Eclipse Foundation (now under name Jakarta EE), including the TCK, so it is free ;) https://jakarta.ee/specifications/jsonp/2.0/ |
Related: jakartaee/jsonb-api#251 |
If we all work together and contribute, I think we can easily make a new version of Jackson that implements the new RFC.
The text was updated successfully, but these errors were encountered: