If you will be announcing these plans here then you will be doing the
proper spec lead work as opposed to giving us a favor
Sergey
On 14/09/16 15:50, Marek Potociar wrote:
> Oracle will be announcing the updated plans with Java EE during J1
> keynote. We can then update the EG mailing list with the announced
> plans for your convenience, so that you do not have to browse around.
>
> Marek
>
>> On 13 Sep 2016, at 22:42, Sergey Beryozkin <sberyozkin_at_talend.com
>> <mailto:sberyozkin_at_talend.com>> wrote:
>>
>> What about the spec leads keeping this list updated as opposed to us
>> browsing around in order to be aware of the plans ?
>>
>> Sergey
>> On 13/09/16 15:36, Marek Potociar wrote:
>>> JavaOne keynote and subsequent JAX-RS related talks next week should
>>> give you the answers that you have been looking for. Stay tuned.
>>>
>>> Marek
>>>
>>>> On 08 Sep 2016, at 18:41, Markus KARG <markus_at_headcrashing.eu
>>>> <mailto:markus_at_headcrashing.eu>> wrote:
>>>>
>>>> Let's see what happens.
>>>> *From:*Sergey Beryozkin [mailto:sberyozkin_at_talend.com]
>>>> *Sent:*Donnerstag, 8. September 2016 10:23
>>>> *To:*jsr370-experts_at_jax-rs-spec.java.net
>>>> <mailto:jsr370-experts_at_jax-rs-spec.java.net>
>>>> *Subject:*Re: [javaee-spec users] [jsr366-experts] update to Java
>>>> EE 8 plan
>>>> I'm finding this quite boring to be honest, seeing the constant
>>>> stream of negative comments. I'd like to stay positive on the
>>>> future of JAX-RS
>>>>
>>>> Sergey
>>>> On 07/09/16 18:06, Markus KARG wrote:
>>>>> Frankly spoken I do not care whom fault it was, as I do very
>>>>> strongly care about the rules of the JCP being harmed by pausing a
>>>>> lot of JSRs for months over and over again.
>>>>> -Markus
>>>>> *From:*Sergey Beryozkin [mailto:sberyozkin_at_talend.com]
>>>>> *Sent:*Dienstag, 6. September 2016 21:57
>>>>> *To:*jsr370-experts_at_jax-rs-spec.java.net
>>>>> <mailto:jsr370-experts_at_jax-rs-spec.java.net>
>>>>> *Subject:*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]
>>>>>> *Sent:*Montag, 5. September 2016 13:42
>>>>>> *To:*jsr370-experts_at_jax-rs-spec.java.net
>>>>>> <mailto: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 <http://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]
>>>>>>>> *Sent:*Dienstag, 23. August 2016 18:16
>>>>>>>> *To:*jsr370-experts_at_jax-rs-spec.java.net
>>>>>>>> <mailto:jsr370-experts_at_jax-rs-spec.java.net>;users_at_jax-rs-spec.java.net
>>>>>>>> <mailto: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
>>>>>>>> <mailto: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
>>>>>>>> <mailto:jsr366-experts_at_javaee-spec.java.net>
>>>>>>>> *Reply-To:*jsr366-experts_at_javaee-spec.java.net
>>>>>>>> <mailto: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/
>>>>>>>
>>>
>>
>