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
Use newer JSON-P & JSON-B standards as alternative to Jackson #29
Comments
That can be done. It only requires changing the JavaTypeDescriptor. However, I have no time to do it now. |
I may try to carve out some time to assist! |
Cool, thanks |
The JSON-P equivalent for @vladmihalcea What is your preference w.r.t. the new type names and package name for the JSON-B/JSON-P types? I've done some initial testing with swapping out Jackson for JsonB/P. Most of the tests are passing but it obviously still needs the aforementioned structural rework: master...JWGmeligMeyling:feature/29 Note: some users may also like that the |
I new type would be fine for JSON-P, like |
Jackson is being obsoleted by JSON-P & JSON-B, and the Java community will be moving forward with the industry standards.
It would be nice to see JSON-P's
JsonObject
orJsonStructure
used instead of Jackson'sJsonNode
.It is also possible that adding in JSON-B could allow for typesafe population of POJOs from PostgreSQL
jsonb
columns, but I can't speak as to whether Hibernate could allow for this level of generics, although I would think it could.The text was updated successfully, but these errors were encountered: