Do keep in mind, JavaOne is a microcosm. It is not necessarily a very good representation of the Java ecosystem at large. Quite honestly the same is true of folks that would take a survey on Java EE.
That being said all of this is of course highly subjective. I suggest doing a quick Twitter survey using neutral language on Oracle social media channels such as @java (Yolande and David copied here for reference).
Sent from my iPhone
> On Mar 21, 2016, at 6:38 PM, Santiago Pericasgeertsen <santiago.pericasgeertsen_at_oracle.com> wrote:
>
>
>> On Mar 21, 2016, at 6:11 PM, Reza Rahman <reza_rahman_at_lycos.com> wrote:
>>
>> I share your concern. I think SSE should remain a vendor specific extension. I really have not seen much demand for it in the community when I talk about it. Most people don't even know what it is yet.
>
> That’s odd because people were very receptive to the idea at J1 last year, and they generally knew the use cases addressed by this protocol.
>
> — Santiago
>
>>
>>> On Mar 21, 2016, at 4:46 PM, Bill Burke <bburke_at_redhat.com> wrote:
>>>
>>> I'm still really concerned about SSE being added to JAX-RS. Is there actual demand for it? Does anybody have support for SSE currently?
>>>
>>>> On 3/21/2016 3:05 PM, Sergey Beryozkin wrote:
>>>> Hi Marek
>>>>
>>>> My colleagues are actively looking at implementing 2.1 SSE draft (based on the link posted to this list earlier on).
>>>> The problem now is that no 2.1 API Snapshot is available,
>>>>
>>>> Copying it from
>>>> https://github.com/mpotociar/api/tree/master/jaxrs-api/src/main/java/javax/ws/rs/sse
>>>>
>>>> is one temporarily workaround, can we do it or we have to wait till the 1st 2.1 API SNAPSHOT
>>>> gets released ?
>>>>
>>>> Thanks, Sergey
>>>>> On 16/03/16 16:21, Sergey Beryozkin wrote:
>>>>> Hi Marek
>>>>>
>>>>> As long as I can see you and Santiago posting, I'm happy and don't mind the schedules much :-).
>>>>> Knowing that 2.1 is alive as a process is enough for me personally
>>>>>
>>>>> Cheers, Sergey
>>>>>> On 16/03/16 13:18, Marek Potociar wrote:
>>>>>> It is very clear right now that we’re not in a shape to deliver according to the current schedule.
>>>>>> I am now discussing with Santiago and our management what would be a revised realistic schedule for JAX-RS 2.1 at this point. Stay tuned - we will post an update on this topic hopefully within a week.
>>>>>>
>>>>>> Cheers,
>>>>>> Marek
>>>>>>
>>>>>>> On 15 Mar 2016, at 13:05, Sergey Beryozkin <sberyozkin_at_talend.com> wrote:
>>>>>>>
>>>>>>> Well, here is what I see at the JSR 370 page:
>>>>>>>
>>>>>>> Q4 2015 Early Draft
>>>>>>> Q1 2016 Public Review
>>>>>>> Q3 2016 Proposed Final Draft
>>>>>>> H1 2017 Final Release
>>>>>>>
>>>>>>> But we do not have an Early Draft at
>>>>>>> https://jax-rs-spec.java.net/
>>>>>>>
>>>>>>> and Q1 is finishing in 2 weeks (as far as Public Review is concerned).
>>>>>>>
>>>>>>> So, it is not clear what the plan is.
>>>>>>>
>>>>>>> Sergey
>>>>>>>
>>>>>>> Q1 2016 Public Review
>>>>>>>> On 15/03/16 11:52, Sergey Beryozkin wrote:
>>>>>>>> Hi Marek, Santiago
>>>>>>>>
>>>>>>>> Is there something we need to know about JAX-RS 2.1 release dates or some JCP process issues that
>>>>>>>> may be 'affecting' JAX-RS 2.1 ?
>>>>>>>>
>>>>>>>> Many thanks, Sergey
>>>
>>> --
>>> Bill Burke
>>> JBoss, a division of Red Hat
>>> http://bill.burkecentral.com
>>>
>