Can't say what it was based on, but there are clearly just a very small
number of "Uber Spec Leads" like Ed or Dmitry from JSON-B (the only EE 8
JSR that went Public Draft so far) who got approval to speak at JavaOne
inside Oracle.
I offered talks on JSR 374 and 375 (together with Ivar) as I am in both
EGs, and the 374 one was approved. For JSR 375 we we were informed, a Kk
Sriramadhesikan, who is not a member of the JSR 375 EG and we never heard
of before ("KK" to many probably sounds more like an author of fantasy
novels;-) does a talk on Security for Java EE 8 and the Cloud.
And Dmitry beside the JSON-B talk also outlines Oracle's ideas for a
Cloud-based Java EE Configuration service. I heard, he reached out to
others who have their own talk on the subject (and based their work on
ideas for standardization presented by others at Oracle some years ago) so
it seems there's interest to keep this standard-based an under the Java EE
umbrella in most cases. Which I'd say is a good prospect.
Werner
On Wed, Sep 7, 2016 at 11:15 AM, <users-request_at_jax-rs-spec.java.net> wrote:
> Table of contents:
>
> 1. [jax-rs-spec users] Re: [javaee-spec users] [jsr366-experts] update to
> Java EE 8 plan - "Markus KARG" <markus_at_headcrashing.eu>
> 2. [jax-rs-spec users] Re: [javaee-spec users] [jsr366-experts] update to
> Java EE 8 plan - Sergey Beryozkin <sberyozkin_at_talend.com>
> 3. [jax-rs-spec users] Re: [javaee-spec users] [jsr366-experts] update to
> Java EE 8 plan - Sergey Beryozkin <sberyozkin_at_talend.com>
>
>
>
> ---------- Forwarded message ----------
> From: Markus KARG <markus_at_headcrashing.eu>
> To: <jsr370-experts_at_jax-rs-spec.java.net>
> Cc:
> Date: Tue, 6 Sep 2016 18:42:21 +0200
> Subject: [jax-rs-spec users] Re: [javaee-spec users] [jsr366-experts]
> update to Java EE 8 plan
>
> I wonder why Ed Burns does the talk. He never was part of the JAX-RS inner
> circle. Also the topic is "suggestions", not "the final answer", which is a
> bit sad. I expected a talk by Marek about "What definitively will be in the
> box".
>
>
>
> Anyways, it is a real pity that few weeks before J1 the JSR 370 Expert
> Group still was not informed about the updated plan. Seems either Oracle
> still has no clue what to tell at J1, or they do not think we are worth
> knowing it before others.
>
>
>
> -Markus
>
>
>
>
>
> *From:* Sergey Beryozkin [mailto:sberyozkin_at_talend.com]
> *Sent:* Montag, 5. September 2016 13:42
> *To:* jsr370-experts_at_jax-rs-spec.java.net
> *Subject:* Re: [javaee-spec users] [jsr366-experts] update to Java EE 8
> plan
>
>
>
> Interesting I was browsing around for more info about the forthcoming
> closure of Java.net and found
>
> https://oracle.rainfocus.com/scripts/catalog/oow16.jsp?
> event=javaone&search=Con7983&search.event=javaone
>
> So if a JAX-RS 2.1 talk is planned then surely some more activity will
> likely to happen soon on this list too :-) ?
>
> Cheers, Sergey
> On 23/08/16 17:38, Sergey Beryozkin wrote:
>
> I think it means it will live.
> I'm not worried right now at all about the missed original schedules.
> We are moving slowly forward, Marek will look at publishing the very 1st
> early 2.1 API soon, and we will
> keep moving from there.
>
> Good news
>
> Sergey
> On 23/08/16 17:29, Markus KARG wrote:
>
> What does that mean for JSR 370? Apparently the original and updated
> schedules are overdue. Will the JSR get restarted? When? With what
> particular target functionality?
>
>
>
> -Markus
>
>
>
>
>
> *From:* Marek Potociar [mailto:marek.potociar_at_oracle.com
> <marek.potociar_at_oracle.com>]
> *Sent:* Dienstag, 23. August 2016 18:16
> *To:* jsr370-experts_at_jax-rs-spec.java.net; users_at_jax-rs-spec.java.net
> *Subject:* Fwd: [javaee-spec users] [jsr366-experts] update to Java EE 8
> plan
>
>
>
> FYI.
>
>
>
> Marek
>
>
>
>
> Begin forwarded message:
>
>
>
> *From: *Bill Shannon <bill.shannon_at_oracle.com>
>
> *Subject: [javaee-spec users] [jsr366-experts] update to Java EE 8 plan*
>
> *Date: *23 August 2016 at 02:05:23 GMT+2
>
> *To: *jsr366-experts_at_javaee-spec.java.net
>
> *Reply-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/
>
>
>
>
>
>
>
>
> ---------- Forwarded message ----------
> From: Sergey Beryozkin <sberyozkin_at_talend.com>
> To: <jsr370-experts_at_jax-rs-spec.java.net>
> Cc:
> Date: Tue, 6 Sep 2016 20:56:42 +0100
> Subject: [jax-rs-spec users] Re: [javaee-spec users] [jsr366-experts]
> update to Java EE 8 plan
> Markus,
> The last thing I'm worried about at this stage is that I have not being
> informed earlier :-). I trust it was not the choice of spec leads not to
> pause the active dev of this spec. I guess it is obvious the whole process
> undergoes significant disruptive changes. If Marek gets out the 1st API out
> to Central I will celebrate (I do believe Marek will do it - he said he
> would look)
>
> Sergey
>
> On 06/09/16 17:42, Markus KARG wrote:
>
> I wonder why Ed Burns does the talk. He never was part of the JAX-RS inner
> circle. Also the topic is "suggestions", not "the final answer", which is a
> bit sad. I expected a talk by Marek about "What definitively will be in the
> box".
>
>
>
> Anyways, it is a real pity that few weeks before J1 the JSR 370 Expert
> Group still was not informed about the updated plan. Seems either Oracle
> still has no clue what to tell at J1, or they do not think we are worth
> knowing it before others.
>
>
>
> -Markus
>
>
>
>
>
> *From:* Sergey Beryozkin [mailto:sberyozkin_at_talend.com
> <sberyozkin_at_talend.com>]
> *Sent:* Montag, 5. September 2016 13:42
> *To:* jsr370-experts_at_jax-rs-spec.java.net
> *Subject:* Re: [javaee-spec users] [jsr366-experts] update to Java EE 8
> plan
>
>
>
> Interesting I was browsing around for more info about the forthcoming
> closure of Java.net and found
>
> https://oracle.rainfocus.com/scripts/catalog/oow16.jsp?
> event=javaone&search=Con7983&search.event=javaone
>
> So if a JAX-RS 2.1 talk is planned then surely some more activity will
> likely to happen soon on this list too :-) ?
>
> Cheers, Sergey
> On 23/08/16 17:38, Sergey Beryozkin wrote:
>
> I think it means it will live.
> I'm not worried right now at all about the missed original schedules.
> We are moving slowly forward, Marek will look at publishing the very 1st
> early 2.1 API soon, and we will
> keep moving from there.
>
> Good news
>
> Sergey
> On 23/08/16 17:29, Markus KARG wrote:
>
> What does that mean for JSR 370? Apparently the original and updated
> schedules are overdue. Will the JSR get restarted? When? With what
> particular target functionality?
>
>
>
> -Markus
>
>
>
>
>
> *From:* Marek Potociar [mailto:marek.potociar_at_oracle.com
> <marek.potociar_at_oracle.com>]
> *Sent:* Dienstag, 23. August 2016 18:16
> *To:* jsr370-experts_at_jax-rs-spec.java.net; users_at_jax-rs-spec.java.net
> *Subject:* Fwd: [javaee-spec users] [jsr366-experts] update to Java EE 8
> plan
>
>
>
> FYI.
>
>
>
> Marek
>
>
>
>
> Begin forwarded message:
>
>
>
> *From: *Bill Shannon <bill.shannon_at_oracle.com>
>
> *Subject: [javaee-spec users] [jsr366-experts] update to Java EE 8 plan*
>
> *Date: *23 August 2016 at 02:05:23 GMT+2
>
> *To: *jsr366-experts_at_javaee-spec.java.net
>
> *Reply-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/
>
>
>
>
>
>
>
>
>
>
> ---------- Forwarded message ----------
> From: Sergey Beryozkin <sberyozkin_at_talend.com>
> To: <jsr370-experts_at_jax-rs-spec.java.net>
> Cc:
> Date: Tue, 6 Sep 2016 20:58:25 +0100
> Subject: [jax-rs-spec users] Re: [javaee-spec users] [jsr366-experts]
> update to Java EE 8 plan
> Ouch, extra 'not', should be
>
> I trust it was not the choice of spec leads to pause the active dev of
> this spec
>
> On 06/09/16 20:56, Sergey Beryozkin wrote:
>
> Markus,
> The last thing I'm worried about at this stage is that I have not being
> informed earlier :-). I trust it was not the choice of spec leads not to
> pause the active dev of this spec. I guess it is obvious the whole process
> undergoes significant disruptive changes. If Marek gets out the 1st API out
> to Central I will celebrate (I do believe Marek will do it - he said he
> would look)
>
> Sergey
>
> On 06/09/16 17:42, Markus KARG wrote:
>
> I wonder why Ed Burns does the talk. He never was part of the JAX-RS inner
> circle. Also the topic is "suggestions", not "the final answer", which is a
> bit sad. I expected a talk by Marek about "What definitively will be in the
> box".
>
>
>
> Anyways, it is a real pity that few weeks before J1 the JSR 370 Expert
> Group still was not informed about the updated plan. Seems either Oracle
> still has no clue what to tell at J1, or they do not think we are worth
> knowing it before others.
>
>
>
> -Markus
>
>
>
>
>
> *From:* Sergey Beryozkin [mailto:sberyozkin_at_talend.com
> <sberyozkin_at_talend.com>]
> *Sent:* Montag, 5. September 2016 13:42
> *To:* jsr370-experts_at_jax-rs-spec.java.net
> *Subject:* Re: [javaee-spec users] [jsr366-experts] update to Java EE 8
> plan
>
>
>
> Interesting I was browsing around for more info about the forthcoming
> closure of Java.net and found
>
> https://oracle.rainfocus.com/scripts/catalog/oow16.jsp?
> event=javaone&search=Con7983&search.event=javaone
>
> So if a JAX-RS 2.1 talk is planned then surely some more activity will
> likely to happen soon on this list too :-) ?
>
> Cheers, Sergey
> On 23/08/16 17:38, Sergey Beryozkin wrote:
>
> I think it means it will live.
> I'm not worried right now at all about the missed original schedules.
> We are moving slowly forward, Marek will look at publishing the very 1st
> early 2.1 API soon, and we will
> keep moving from there.
>
> Good news
>
> Sergey
> On 23/08/16 17:29, Markus KARG wrote:
>
> What does that mean for JSR 370? Apparently the original and updated
> schedules are overdue. Will the JSR get restarted? When? With what
> particular target functionality?
>
>
>
> -Markus
>
>
>
>
>
> *From:* Marek Potociar [mailto:marek.potociar_at_oracle.com
> <marek.potociar_at_oracle.com>]
> *Sent:* Dienstag, 23. August 2016 18:16
> *To:* jsr370-experts_at_jax-rs-spec.java.net; users_at_jax-rs-spec.java.net
> *Subject:* Fwd: [javaee-spec users] [jsr366-experts] update to Java EE 8
> plan
>
>
>
> FYI.
>
>
>
> Marek
>
>
>
>
> Begin forwarded message:
>
>
>
> *From: *Bill Shannon <bill.shannon_at_oracle.com>
>
> *Subject: [javaee-spec users] [jsr366-experts] update to Java EE 8 plan*
>
> *Date: *23 August 2016 at 02:05:23 GMT+2
>
> *To: *jsr366-experts_at_javaee-spec.java.net
>
> *Reply-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/
>
>
>
>
>
>
>
>
>
>
> End of digest for list users_at_jax-rs-spec.java.net - Wed, 07 Sep 2016
>
>