JSON-P (Java API for JSON Processing - JSR-353) provides a portable standard solution to parse, generate, transform, and query JSON using 2 APIs, a streaming API and an object model API based on the streaming API. JSON-P was one of the API added to Java EE7.
But clearly JSON parsing and JSON generation was a first step and only a (important) part of the global equation. To convert Java objects from/to JSON representation, you have to rely on different solutions, different frameworks such as EclipseLink MOXy or Google GSON to just name two! The issue is that, obviously, all those frameworks are all different since there is no standard in that space. This was also clearly reflected in the Java EE 8 Community Survey as JSON Binding was the most asked feature!
Oracle plans to submit a new JSR to solve that particular problem, i.e. the 'Java API for JSON Binding' JSR. The JSON-B JSR aims to define a standard binding layer for converting Java objects to JSON messages and vice versa. JSON-B will leverage and complement JSON-P (JSR 353). The draft proposal for the JSON-B JSR has just been made public to gather feedback and recruit supporters before it is submitted to the JCP in August. JSON-B will be targeted for inclusion in Java EE 8 but will also work with Java EE 7. And timing wise, it is aligned with the current Java EE 8 roadmap.
It's summer time and August isn't that far, so make sure to read the proposal and gives us your feedback quickly!
Podcasts & Videos
- Developers Continue to Affirm Strong Support for Java EE 7
- Self-Documented Services Using JAX-RS Analyzer
- Java SE 8 and Java EE 7 in Production at TecSinapse
- Java EE @ ConFoo 2016
- The next VTS round is fast approaching!
- Java EE 7 Proves Effective for Mission-Critical E-Payment Systems
- Java EE @ DevNexus 2016
- Java EE in Practice for Secure Online Voting at Scytl
- Cargo Tracker Java EE 7 Blue Prints Now Running on WebLogic
- Revamping the Security API in Java EE 8