Tuesday Jul 15, 2014
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
- Some Interesting Real World CDI Usage Statistics
- Migrating from Java EE 5 to Java EE 7 at Segurnet Portugal
- HTTP/2 and Servlet 4 in Java EE 8
- EJB3 @Lock Annotation for CDI Beans
- Java EE @ Oredev
- Migrating from Tomcat to Java EE and TomEE at Dassault Systemes
- AngularBeans: Java EE 7/CDI Integration with AngularJS
- Java EE @ Java Day Mexico
- Hypermedia/HATEOAS Support in JAX-RS 2/Java EE 7
- Java EE in Practice at Lufthansa Industry Solutions