JEP 198: Light-Weight JSON API

[Otávio Gonçalves de Santana]

Hi everyone.
Is there any reason to not implement the JSR that already exist and that
was born?

https://jcp.org/en/jsr/detail?id=367
https://jcp.org/en/jsr/detail?id=353

Which especific cases what the OpenJDK need and this JSR don't care?
Why just work together with these JSRs and each one has your implementation?
For example, one to OpenJDK and another to JavaEE, this way each one
implements according your necessity.

The question is: it's really make sense have two APIs with similar goal? It
would great to the Java developer should to know two API to do the same
thing?


obs: Sorry to question a lot, I just would like know more to be more useful.




On Thu, Jul 31, 2014 at 1:28 AM, Mario Torre <neugens.limasoftware at gmail.com
> wrote:

> I never gave a +1 with more enthusiasm! :)
>
> Cheers,
> Mario
> Il 31/lug/2014 03:27 "Wang Weijun" <weijun.wang at oracle.com> ha scritto:
>
> >
> > On Jul 31, 2014, at 8:35, Remi Forax <forax at univ-mlv.fr> wrote:
> >
> > >
> > > On 07/25/2014 04:45 PM, mark.reinhold at oracle.com wrote:
> > >> New JEP Candidate: http://openjdk.java.net/jeps/198
> > >>
> > >> - Mark
> > >
> > > Hi Mark, Hi Mike,
> > > Implementing a json API was one of the use case I've used during the
> > development of the lambdas,
> > > so maybe you are interested by this gist
> > >  https://gist.github.com/forax/81a56cf2684bfa2e46ec
> >
> > I am reading "[ \"foo\", \"bar\" ]" and feel we need a JEP for new styles
> > of literal strings. Long long ago there was a proposal for multi-line raw
> > strings. Still alive?
> >
> > Thanks
> > Max
> >
> >
> >
>



-- 
Otávio Gonçalves de Santana

blog:     http://otaviosantana.blogspot.com.br/
twitter: http://twitter.com/otaviojava
site:     *http://about.me/otaviojava <http://about.me/otaviojava>*
55 (11) 98255-3513