@Hendrik: too early to merge it or can we have a jsonp 1.1 impl? Wonder if we can get a jsonp 1.0 support still with 1.1 features as internals for the mapper and 1.1 support if the API is there. Does it sound possible testing the API in the "factories"?
Romain Manni-Bucau @rmannibucau | Blog | Github | LinkedIn | Tomitriber 2016-03-25 14:59 GMT+01:00 Hendrik Dev <[email protected]>: > s that needed for jsr-374 (jsonp 1.1) only or also for jsr-353 (jsonp 1.0) > currenty johnzon jsonp 1.1 impl is here > https://github.com/apache/incubator-johnzon/tree/jsr374_367 > > On Tue, Dec 8, 2015 at 8:56 AM, Romain Manni-Bucau > <[email protected]> wrote: >> answering to myself, jsonp 1.1 got readValue() instead of readStructure() >> so we have to update our parser. >> >> >> Romain Manni-Bucau >> @rmannibucau <https://twitter.com/rmannibucau> | Blog >> <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> >> | >> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber >> <http://www.tomitribe.com> >> >> 2015-12-07 17:41 GMT+01:00 Romain Manni-Bucau <[email protected]>: >> >>> Hi guys >>> >>> seems jsonb wants to supports plain vaules (or wrapped in Optional) >>> >>> I'm not a big fan of it and our parser doesnt ATM, do we go this path or >>> do we push on the spec side to remove it? >>> >>> Romain Manni-Bucau >>> @rmannibucau <https://twitter.com/rmannibucau> | Blog >>> <http://rmannibucau.wordpress.com> | Github >>> <https://github.com/rmannibucau> | LinkedIn >>> <https://www.linkedin.com/in/rmannibucau> | Tomitriber >>> <http://www.tomitribe.com> >>> > > > > -- > Hendrik Saly (salyh, hendrikdev22) > @hendrikdev22 > PGP: 0x22D7F6EC
