I'm just about to ask Heather, all EG members who are known to be there are
CC so we can find a date that's best for everyone (e.g. nobody having a
talk ;-D)
Werner
On Wed, Aug 24, 2016 at 11:16 AM, Ivar Grimstad <ivar.grimstad_at_gmail.com>
wrote:
> +1 to a F2F meeting!
>
> On Wed, Aug 24, 2016 at 11:14 AM Werner Keil <werner.keil_at_gmail.com>
> wrote:
>
>> Guys,
>>
>> I'm not sure, if Jeff is likely Oracle's new Spec Lead for JSR 375 or
>> just a "messenger", but the message for this JSR and its goals towards Java
>> EE 8 at least include "O-Auth and OpenID Connect support" by the time the
>> EE 8 release train is scheduled.
>>
>> David already spoke about possible adjustments to the exact scope or
>> requirements of JSRs like 375 when he mentioned it at JavaLand, but he also
>> called it "Cloud relevant" and so did other sources at Oracle. And it is
>> quite unlikely the aims like
>>
>> "O-Auth and OpenID Connect" can be reached elsewhere.
>> Java EE 8 is supposed to run on Java SE 8, so a new "JEP" or SE 9 module is out of the question.
>> JSR 351 (Identity Management where AFAIR OpenID was also experimented with) was withdrawn by Spec Lead Oracle,
>> which leaves JSR 375 as its natural heir and successor.
>> spoke
>>
>> Many of us including Ivar, Adam, David or myself are speakers at JavaOne.
>> Red Hat, IBM and Oracle will obviously be there, too, regardless of the inviduals representing them in the EG.
>>
>> Are those who come to JavaOne happy to do a F2F meeting offered by Heather to Spec Lead and Experts?
>>
>> Sorry that Arjan does not seem to be there, but I recall the conference rooms have both audio and Wifi, so ideally he and others who cannot attend in person could also join the meeting by phone, Skype or Hangout.
>>
>> Cheers,
>>
>>
>> Werner
>>
>>
>> On Tue, Aug 23, 2016 at 2:31 AM, Jeff Tancill <jeff.tancill_at_oracle.com>
>> wrote:
>>
>>> FYI
>>>
>>>
>>>
>>> -------- Forwarded Message --------
>>> Subject: [javaee-spec users] [jsr366-experts] update to Java EE 8 plan
>>> Date: Mon, 22 Aug 2016 17:05:23 -0700
>>> From: Bill Shannon <bill.shannon_at_oracle.com> <bill.shannon_at_oracle.com>
>>> Reply-To: jsr366-experts_at_javaee-spec.java.net
>>> To: jsr366-experts_at_javaee-spec.java.net
>>>
>>> As many of you have read in the press [1], Oracle is reevaluating the
>>> scope and plans for Java EE 8. Based on the changes we've seen in the
>>> industry in recent years, we believe we need to do more to Java EE to
>>> make it better suited for developing the next generation of cloud
>>> and microservices applications.
>>>
>>> The current generation of enterprise Java applications is already well
>>> supported by Java EE 7 in cloud services provided by Oracle and
>>> others. As Anil Gaur said in his recent presentation to the JCP EC [2]:
>>>
>>> We would like the future of Java EE to be viable to next generation
>>> of applications. These apps are composed and deployed differently
>>> in cloud and require flexibility, reliability and scale. The
>>> platform needs a new programming model that's geared towards
>>> reactive style programming for building large-scale distributed
>>> applications that are loosely coupled. In addition, we would like
>>> to see HTTP/2, Config, State management, Eventual Consistency,
>>> Multi-tenancy, O-Auth and OpenID Connect get included in the
>>> platform.
>>>
>>> It is critical that Java EE reflect the needs of the community. We are
>>> preparing another community survey, similar to the survey we did in
>>> 2014 [3], to assess whether the community shares our views about
>>> what's needed in Java EE. We expect this survey to be available in
>>> the next few weeks. We'll also be looking at the results of other
>>> surveys and community input, and will be continuing our discussions
>>> with Java EE licensees. At JavaOne we'll be presenting our proposals
>>> for updates to Java EE and gathering feedback from attendees.
>>>
>>> After considering the results of our survey and other feedback, we'll
>>> adjust the plans for Java EE 8, with a goal of delivering Java EE 8
>>> within a year. Much of the initially planned work is nearly complete
>>> or well on its way, but new work will need to be done more quickly than
>>> usual. Obviously all desired work will not be able to be done in Java
>>> EE 8 and some planned work may no longer be important.
>>>
>>> This short schedule for Java EE 8 will allow us to move quickly into
>>> planning for Java EE 9, which will be able to take advantage of the
>>> Java SE 9 Jigsaw module system, and will give us more time for some of
>>> the larger improvements to the Java EE programming model.
>>>
>>> Stay tuned for more information about our community survey, and join us
>>> at JavaOne to hear more about our proposals for Java EE.
>>>
>>> Your opinion is valuable to us and we look forward to collaborating with you.
>>>
>>>
>>> [1]http://www.infoworld.com/article/3098007/java/oracle-to-reboot-java-ee-for-the-cloud.html
>>> [2]https://jcp.org/aboutJava/communityprocess/ec-public/materials/2016-08-09/August-2016-Public-Minutes.html
>>> [3] https://blogs.oracle.com/ldemichiel/
>>>
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Java EE Security API - JSR 375 - Experts" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jsr375-experts+unsubscribe_at_googlegroups.com.
>> To post to this group, send email to jsr375-experts_at_googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/
>> msgid/jsr375-experts/CAAGawe2oSmPmLiN8_sRzbD9QxNE0feYwf_
>> xkQOc0imksZ6G%2B_Q%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jsr375-experts/CAAGawe2oSmPmLiN8_sRzbD9QxNE0feYwf_xkQOc0imksZ6G%2B_Q%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>