When Oracle announced that MVC 1.0 was withdrawn from Java EE 8, they also indicated that they were investigating a possible transfer to a community member or organization for completion as a standalone JSR. True to their word, a request for a transfer ballot of JSR 371 has now been submitted to the JCP Executive Committee.
I am happy to announce that I will be the receiving part of this transfer and thus will take over as Spec Lead for JSR 371.
So, why would I want to take over a JSR that ranked so low in the Java EE Survey? Well, there are several reasons for that:
First of all the incredible community support and interest there is for MVC 1.0. For example, JSR 371 is the most widely adopted JSR by Java User Groups participating in the Adap-a-JSR program. No less than 8 JUGs have adopted this JSR!
Secondly, I feel that the wording of the question in the survey may have played a role. The question for MVC was “How important is MVC API for the next generation of cloud and microservices applications? (1=Not Important, 2, 3, 4, 5=Very Important)”. Still, 505 responded Very Important and only 361 Not Important. The rest were pretty evenly distributed. See Java EE Survey Results for the complete numbers.
Third, only 1693 surveys were completed worldwide. Out of 10 million Java developers, this is an alarmingly low number taking into consideration that the survey was open for more than a month and there were massive encouragements for participation from the community, including Oracle.
Fourth, in the Java EE Guardians survey that was performed just prior to the Java EE 8 survey more than 30% of the respondents answered Very Important to the question “How important is it to add a new action-oriented MVC framework to Java EE?”.
The Way Forward
The most important thing right now is that the request for transfer is approved by the EC. The ballot closes January 30, so shortly after that the practical work may start.
…and looking forward to 2017!
2016 was a pretty eventful and great year for me personally. I had the opportunity to speak at a number of conferences including Jfokus, JavaLand, GIDS, CybercomDev, jPrime, Devoxx UK, JavaDay Minsk, JavaOne, JavaDay Kiev, Devoxx MA, Øredev. Links to talks and videos for most of these talks can be found on my Speaker Bio page.
I will continue speaking at conferences and events throughout 2017 as well. First up are Snowcamp.io, Devnexus, jDays, JavaLand, Riga Dev Days, DevDays Vilnius. And I still have some CFPs to submit talks to…
I also took over as JUG leader of Javaforum, the Java User Group in Malmö, and we had four meetings during 2016. The goal for 2017 is to continue with one meeting each quarter.
At the end of the year I won one of the associate seats in the Executive Committee of the Java Community Process. I am really looking forward to starting this work (I am actually going to London for our first face-to-face meeting tomorrow…).
If I should pick one single thing as the highlight of 2016, it would be the accepted to join the Java Champions. It was a surprise and an honor to be handed the Java Champions jacket from Arun Gupta at the closing Keynote of Devoxx UK.
You have probably noticed that the Java Community Process (JCP) has made becoming a member much easier. There is a new membership level called Associate Member which does not require any paperwork or approval of your employer and it can all be done online filling out a simple form.
Why should you become a member?
– It looks good on your resume
– You can join as a contributor to any JSR and help evolve the Java ecosystem
– You get a vote in the upcoming elections for the Executive Committee
Why is the last item important?
Well, I am running for an associate seat in the EC, so by joining the JCP and voting for me in the upcoming election, you make sure that your voice is heard at the very top level of the JCP. My motivation is to give as much power to the community as possible.
Let’s make the JCP Great Again!
Please feel free to contact me on Twitter or discuss in the comment section if you have any questions or comments.
The Java Community Process (JCP) program 2016 Executive Committee (EC)
Elections have started. This is the first election to be held under the newest JCP 2.10 Process Document rules.
One of the new things introduced is that there will be two Associate Seats in the Expert Committee. These seats are elected by the Associate members of the JCP.
I have nominated myself for one of these Associate Seats. See my position statement below.
JCP EC 2016 Position Statement
I don’t think anybody with the slightest interest in server-side Java™, and Java EE in particular, have missed the frustrations (and anger) in the community for the hiatus regarding the specification work of Java EE 8. The activity for most of the Java EE 8 targeted JSRs have more or less stagnated for almost a year, with only a few exceptions.
This has resulted in initiatives such as the Java EE Guardians and the Microprofile.io. Both emerging from a community eager to move Java EE forward to continue being the preferred platform for enterprise Java™.
The minutes from the August meeting in the JCP Executive Committee indicates that Oracle is finally beginning to move. At the meeting, Anil Gaur, Oracle Group Vice President with responsibility for Java EE and WebLogic Server, said:
“…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…”
This year’s JavaOne will definitely be exciting in terms of Java EE. If you haven’t registered yet, do so!
I am carefully optimistic and think that Java EE has a bright future!
I am extremely proud and honored to be included in this exclusive group of Java dignitaries.
The Java Champions are an exclusive group of passionate Java technology and community leaders who are community-nominated and selected under a project sponsored by Oracle. Learn more about Java Champions.
The JPA Modeler plugin for NetBeans provides visual support for creating, designing and editing entity relationship models. It also provides Java code generation and new for version 1.5.5 is that it provides support for generating MVC 1.0 applications.
Check out MVC 1.0 Generator Tutorial to see how it works.
Kudos to Gaurav Gupta (@jGauravGupta) for this awesome tool! Another proof that NetBeans is the IDE for developing Java EE applications!
Follow @jpamodeler on Twitter!
I am pleased to announce that I will take over as JUG leader in the Malmö branch of Javaforum in Sweden. As a first step we will follow our friends from the other locations in Sweden and move to Meetup. The old site at http://jforum.se has been around for 10 years and time has come to try out some more modern options.
Make sure you register yourself to stay up-to-date on what’s going on in your local Java Community.
Thanks to Cybercom for sponsoring the Meetup subscription.
It is great to start 2016 with the announcement that I have been included in the NetBeans Dream Team!
I always try to be as objective and unbiased as possible when writing and talking about tools and technologies, but I guess it has been pretty obvious that NetBeans is my favorite IDE and in my opinion the best IDE for Java EE development. Being a member of the Dream Team will enable me to contribute even more to make this great tool even greater.
More information about the NetBeans Dream Team can be found on the wiki.
SnoopEE [ˈsnuːpı] – The lean and simple discovery mechanism for Java EE based microservices.
What’s in a name, really?
Naming is hard! When I came up with the name Snoop for my discovery mechanism for microservices based on Java EE, my though was to associate the name with “snooping around for services to discover”. It seems, however, that most people’s thought goes to Snoop Dogg when hearing the name and that was never my intention.
That is one of the reasons for the renaming. Another consideration is that I want to point out that the best fit for SnoopEE is for Java EE!
At the same time I don’t want to signal that it is only for Java EE. I want it to be just as lean and simple no matter what technology used to implement the services. That is the only reason why I have been a little reluctant to the renaming.
SnoopEE has a nicer feel and as the twitter poll indicates, I am not alone thinking this.
For the record, I have nothing at all against Snoop Dogg! I just feel that Snoopy the dog is a little bit cuter…
I have crated a new page for SnoopEE, but as for everyhing else, such as GitHub repo, maven coordinates and naming, it all stays as it is until properly announced otherwise.