The only upside is, should others relieve Oracle of Spec Lead Duty, then an Open Source RI and TCK is much easier, than if Oracle does it. Dmitry does JSON-B or JSON-P RI in the Open, but both keep their closed TCKs.
Should IBM and Red Hat, both played with ideas and concepts in Microprofile, consider filing a JSR it could have a good chance of an Open Source approach like CDI, Bean Validation or JBatch. Cheers, Werner On Fri, Dec 23, 2016 at 1:18 AM, P. Ottlinger <[email protected]> wrote: > Hi, > > bad news for now ... > > Am 23.12.2016 um 01:14 schrieb Anatole Tresch: > > It is incredible, but it is reality again. No config JSR again for EE8... > > let's focus on our project and microprofile.io. > > That's how I interpreted the PDF snippet from Werner: > > "... > At JavaOne, we had proposed to add Configuration and Health > Checking to Java EE 8, and these > technologies rank reasonably high in survey results. However, after > additional review we believe > the scope of this work would delay overall Java EE 8 delivery. We have > concluded it is best to > defer inclusion of these te > chnologies in Java EE in order to complete Java EE 8 as soon as > possible. > ...." > > This gives us more chances :-) > > Cheers, > Phil >
