Btw.
Somebody (probably Ivar or David) created the Github organization similar
to those for other JSRs (most recently JSON-B or JSON-P also did) The page
repo is still empty, others like "sandbox" probably make less sense, but
even if JMS 2.1 is withdrawn, I assume the history and documentation of JMS
2.0 and before must survive the java.net shutdown?
Any plans for that?
Regards,
Werner
On Thu, Oct 6, 2016 at 11:55 AM, Werner Keil <werner.keil_at_gmail.com> wrote:
> Nigel/all,
>
> Thanks for the update.
> I was like a few other EG members in Linda's talk as well as the keynote.
> And we also heard in the EC F2F more or less what was later unveiled and
> discussed.
>
> Having multiple ways of messaging (aside from JMS, CDI, Websockets or
> JAX-RS were explicitly mentioned in some of the Java EE sessions) does put
> JMS in a more "legacy" position.
>
> And I personally faced in a recent project that where it's heavily used,
> the platforms and environments often keep solutions restricted to older
> versions of Java EE like 6 or even 5 with the respective JMS releases.
>
> In a "Cloud Native" world messages are more often exchanged via API calls
> or e.g. Web Sockets than JMS or (IBM) MQ. Therefore I can understand it,
> though I had hoped we could streamline some aspects like CDI events and JMS
> with this JSR.
>
> Regards,
>
> Werner Keil | JCP Executive Committee Member, JSR 363 Maintenance Lead |
> Eclipse UOMo Lead, Babel Language Champion | Apache Committer
>
> Twitter @wernerkeil | @UnitAPI | @JSR354 | @AgoravaProj | @DeviceMap
> | #DevOps | #EclipseUOMo
> Skype werner.keil | Google+ gplus.to/wernerkeil
>
>
>
> On Thu, Oct 6, 2016 at 3:13 AM, <users-request_at_jms-spec.java.net> wrote:
>
>> Table of contents:
>>
>> 1. [jms-spec users] The future of JMS 2.1 and Java EE 8 - Nigel Deakin <
>> nigel.deakin_at_oracle.com>
>>
>>
>>
>> ---------- Forwarded message ----------
>> From: Nigel Deakin <nigel.deakin_at_oracle.com>
>> To: "users_at_jms-spec.java.net" <users_at_jms-spec.java.net>
>> Cc:
>> Date: Wed, 5 Oct 2016 09:47:47 +0100
>> Subject: [jms-spec users] The future of JMS 2.1 and Java EE 8
>> As everyone will know, several Oracle-led JSRs (including JMS 2.1) have
>> made little progress this year due to the spec leads being diverted partly
>> or wholly to work on other things.
>>
>> At JavaOne last month Linda DeMichel, Java EE joint spec lead, gave an
>> update on progress and plans for Java EE 8.
>> You can watch the whole presentation online here:
>> https://www.youtube.com/watch?v=Th9faGLhQoM
>> or you can simply review the slides here:
>> https://java.net/downloads/javaee-spec/JavaEE8Update.pdf
>>
>> Linda's presentation proposes a shift in focus for Java EE, to reflect
>> recent developments in the industry, which she summarised as a "focus on
>> deployment into the cloud", a "focus on microservices", and an "emphasis on
>> more rapid evolution of applications".
>>
>> In order to address these changes, and modernise Java EE 8 for "cloud and
>> microservices", she proposed a two-fold approach:
>>
>> * Adjust the plan for Java EE 8
>> * Create a plan for, and start work on, Java EE 9
>>
>> Java EE 8 and JMS 2.1
>> ---------------------
>>
>> Linda confirmed the plan to complete Java EE 8 in 2017 as originally
>> proposed, but with a number of changes to its content. These are listed in
>> slides 27 and 28 of her slide deck.
>>
>> The Java EE 8 JSR and most of its constituent JSRs would continue as
>> originally planned. She proposed that two new constituent JSRs be added,
>> for health checking and for configuration.
>>
>> And she proposed to drop three of the existing constituent JSRs: MVC 1.0
>> (JSR 371), Management 2.0 (JSR 373) ... and JMS 2.1 (JSR 368).
>>
>> The reason for dropping JMS 2.1 was that JMS was "no longer very relevant
>> in cloud". JMS would continue to be part of Java EE 8, but at its current
>> version JMS 2.0 rather than at a new version JMS 2.1.
>>
>> Java EE 9
>> ---------
>>
>> Linda went on to propose a plan for Java EE 9, which would focus more
>> directly on the new requirements, with work running in parallel with Java
>> EE 8 and with a release date of 2019. Please see Linda's slides for more
>> details, and if you'd like to find out more about Java EE 9 I would
>> recommend watching a couple of JavaOne presentations:
>>
>> Rajiv Mordani, Josh Dorr, Dhiraj Mutreja -- Enterprise Java for the Cloud
>> https://www.youtube.com/watch?v=t7miysQP7Dg
>> Josh Dorr, Joe Di Pol, Rajiv Mordani -- Portable Cloud Applications with
>> Java EE
>> https://www.youtube.com/watch?v=nCqVSf5v37s
>> There are two presentations because there was too much material to fit
>> into a single presentation. They include some proposals for a new
>> "eventing" JSR in Java EE 9 which I suspect will be of particular interest.
>>
>> Your views
>> ----------
>>
>> Your views on all of these proposals are invited.
>>
>> You can make comments on proposal to drop JMS 2.1 from Java EE 8 here (
>> users_at_jms-spec.java.net) or you can reach a wider audience by sending
>> them to the Java EE users mailing list (users_at_javaee-spec.java.net). You
>> can sign up to the latter at https://java.net/projects/javaee-spec/lists
>>
>> Comments on the proposals for Java EE 9 (including the "eventing"
>> proposals) should be made to the Java EE users mailing list.
>>
>> In addition, the Java EE spec leads have launched a new Java EE community
>> survey. Please do take part and give your views on the future of Java EE.
>> This is at http://glassfish.org/survey . The survey closes on 21 Oct
>> 2016. This will be followed by a second survey that allows people to
>> prioritise the top items from the first survey.
>>
>>
>> Nigel
>> (JMS 2.1 spec lead)
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> End of digest for list users_at_jms-spec.java.net - Thu, 06 Oct 2016
>>
>>
>