Open hohwille opened 9 years ago
I found that we have code in our sample that is directly using jackson in TOs what is undesired. Proprietary dependencies in business objects is not nice. We should do that if we have a reliable standard.
According to the roadmap, we have to wait until around August 2015 till we can migrate to JSON-B. JSR 367 review is complete on 08 Sep, 2014
JSON-P is already available: http://repo1.maven.org/maven2/javax/json/javax.json-api/1.0/ and there are OSS implementations, e.g.: https://jsonp.java.net/
JSON-B still takes some time but as soon as it is available and a reliable implementation is available, we should have a look. This is one of the black spots where we currently lack a standard and are tight to jackson as implementation (it does its job good, but we want to use standards where ever possible and give freedom for people to exchange the implementation if they really need to).