[jax-rs-spec users] Re: [javaee-spec users] [jsr366-experts] update to Java EE 8 plan

From: Markus KARG <>
Date: Sat, 17 Sep 2016 18:40:04 +0200

I agree with that, but how does Oracle let us help to reach that target
right now in this very moment?



From: Sergey Beryozkin []
Sent: Freitag, 16. September 2016 23:22
Subject: Re: [jax-rs-spec users] [javaee-spec users] [jsr366-experts] update
to Java EE 8 plan


It has been very frustrating for all of us, I know.
What I meant is that keeping talking about Oracle is not something that can
make JAX-RS stay competitive. We have no time for it.
The process is about to get back to life. JAX-RS will need to keep itself
relevant to what the users need to do today, everyone is talking about
async, reactive calls, etc, that what I meant.

On 16/09/16 18:40, Markus KARG wrote:


.and you really think that suspending JAX-RS for months against the EGs
will, being not responsive for that time, and finally not letting have the
EG a say in the target features of JAX-RS 2.1 until J1 started is the best
way to make JAX-RS stay relevant to the practical user? Or what do you like
to tell us with that last comment?




From: Sergey Beryozkin []
Sent: Freitag, 16. September 2016 15:02
Subject: Re: [jax-rs-spec users] [javaee-spec users] [jsr366-experts] update
to Java EE 8 plan


In JAX-RS 2.0 Client API was the main new addition, with a host of various
'minor' additions like AsyncResponse.
To be honest I'm not sure it was up to us to accept or reject whether we
wanted Client API or not - but no doubt Client API was needed.

Initial 2.1 enhancements, particularly client side Rx invokers will be a
very good addition. I've no idea right now what else the future 'blueprint'
may require from JAX-RS. The most important thing right now is to ensure
JAX-RS will stay relevant to the practical users.


On 15/09/16 21:43, Markus KARG wrote:

Sergey, we should finally understand that it is not Oracle's plan to let
this expert group actualy *develop* the next release of the JAX-RS standard,
but that the JCP is only there to put an "approved" stamp on what somebody
at Oracle already has in his drawer. While this is not what the community
expects from a democratic institution in general or the JCP in particular, I
think neither the EG nor the spec leads can change that policy. :-(



From: Sergey Beryozkin []
Sent: Mittwoch, 14. September 2016 16:53
Subject: Re: [jax-rs-spec users] [javaee-spec users] [jsr366-experts] update
to Java EE 8 plan


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

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.




On 13 Sep 2016, at 22:42, Sergey Beryozkin <> wrote:


What about the spec leads keeping this list updated as opposed to us
browsing around in order to be aware of the plans ?

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.




On 08 Sep 2016, at 18:41, Markus KARG <> wrote:


Let's see what happens.


From: Sergey Beryozkin []
Sent: Donnerstag, 8. September 2016 10:23
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

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.



From: Sergey Beryozkin [ <>]
Sent: Dienstag, 6. September 2016 21:57
To: <>
Subject: Re: [javaee-spec users] [jsr366-experts] update to Java EE 8 plan


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)


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


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.





From: Sergey Beryozkin [ <>]
Sent: Montag, 5. September 2016 13:42
To: <>
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 <> and found


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

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?





From: Marek Potociar [ <>]
Sent: Dienstag, 23. August 2016 18:16
To: <>; <>
Subject: Fwd: [javaee-spec users] [jsr366-experts] update to Java EE 8 plan





Begin forwarded message:


From: Bill Shannon < <>>

Subject: [javaee-spec users] [jsr366-experts] update to Java EE 8 plan

Date: 23 August 2016 at 02:05:23 GMT+2

To: <>

Reply-To: <>


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

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

[3] <>