& Ldquo; Last year, Oracle's Java missionaries layoffs, even earlier announced that it would temporarily stop the large-scale version of the update released GlassFish Server and related support restrictions. For a time the printing of rumors: Oracle will abandon Java? What will happen tomorrow in the Java community? Through the power of Java EE Rise of the Guardians of Rescue Java EE
As of last year, Oracle Java missionaries layoffs, and even earlier announced that it would temporarily stop publishing for the GlassFish Server and related support large-scale version of the update to be limiting, a group of supporters began to Java Standard & ldquo; Java EE Guardian & rdquo; identity itself, and by a statute declared they will try to save Java EE.
Java EE is a true Java guardian authority, whose members include & ldquo; Java father & rdquo; James Gosling, former technical missionaries Reza Rahman, and many other well-known Java technical staff.
The founder of the group, Java EE / GlassFish former missionary Reza Rahman said:
Currently we gathered nearly 400 members of Google Group, our Twitter account has nearly 2,000 followers.
While employed by Oracle, the & ldquo; infantry & rdquo; still trying to promote Java technology continues to develop. However, the statistics show they provide Java EE development boom is facing a severe recession. We can clearly see from the chart provided on their website, the number of submissions has solved both the downward trend in the number and version issues.
According to Oracle's excuse that the company seems to have fully turned to the future direction of the cloud.
Although Java EE Guardian also recognizes the importance of cloud computing, but they also said:
Nevertheless, there are still more and more evidence that Oracle is very clear disregard Java EE, undermine skilled Java EE developers created perfect ecosystem. Except in the case of a turnaround soon, otherwise the matter in accordance with the initial promise can be smoothly released, Java EE 8 is likely to be delivered within the foreseeable future.
Why Oracle take this neglect attitude that will last long and in the end, these things are hard to say. Even in the face of the most & ldquo; intimate & rdquo; partners, Oracle did not disclose their motives, leaving only the entire community to fend for themselves. There is a possibility that the very disturbing, Oracle is doing to moving away from collaborative development approach based on open standards, into the pursuit of a highly proprietary unidirectional method.
Java EE guardian of the constitution is the pursuit of a more & ldquo; & rdquo ;, rational strategy hopes to provide support for the entire industry & ldquo; to solve this thorny problem & rdquo ;:
As promised, we still need to Oracle this volume, scope of business, company size and resources to exert the necessary influence. Convince Oracle fully into account external users (even its customers) the legitimate rights and interests, past experience proved that this method is fraught with challenges. This still continues to do so may not be a great success, but we must always maintain adequate and rational optimism. Java EE community needs your help. We need to support your opinion, even if possible you need to pay a certain amount of time to volunteer to help us to achieve this success. You can help us in various ways.
From Oracle's perspective, it may feel not worth to continue to provide support for Java EE or other Java technologies.JavaFX still do not get enough attention as expected, NetBeans IDE is still only a 10% market share. InfoQ asked to Rahman for not achieve & ldquo; the escape velocity & rdquo; technology continues enormous investment value that can be obtained:
I can tell you is that, Netbeans is a very beautiful IDE. As long as the proper use, NetBeans can be successful.
JavaFX is not a beginning of how elegant the API, and then subsequent improvement and it seems not much room for improvement. But this technology is not to be bad to the point where we abandoned. Car dashboard may run on JavaFX, browsers may be so. A need for a front-end Java technology, JavaFX and TLC complex fill this gap.
Mobile field too, although there are problems, but there is still a need to continue to refine and improve, there are also a lot of companies are willing to continue to improve the technology, because there still exists the problem space (Problem space).
Java EE stand still: Java community can turn things around?
Recently we focus on Oracle's commitment to Java EE There are a lot of concerns. Pivotal company Spring Data JPA 2.1 Expert Group project director and a member of Oliver Gierke recently referred to Jaxenter Oracle has clearly lost interest in Java EE 8, also describes the effects of these conditions may be generated by the Java community.
Java EE 7 is released after a few months, Oracle released in November 2013 published a blog post about the roadmap for Java EE 8:
After the release of Java EE 7 and GlassFish Server Open Source Edition 4, we start planning for Java EE 8 roadmap and by JavaOne Strategy keynote introduced. In conclusion, our interest focused on improved support for HTML5, cloud computing and NoSQL support for the investigation of other aspects. For everyone in the Java EE 8 want to see improvements in the community and provide some great feedback for us.
Simply put, Oracle Java EE for the future to make a commitment. Java EE 7 has been officially released, Java EE 8 also work on planning has begun.
After that, Oracle in the blog post showing enthusiasm seems to be completely shut down the.Oracle in June 2015 to publish a blog post Java community notification about the status of the latest Java EE 8 roadmap:
Goals we have set for ourselves is to complete the related work before JavaOne San Francisco 2016 start. Although we all like to make at JavaOne (and hear) some big things, but the other requirements of the various delays encountered during startup expert group as well as our specification manager encountered in time lead to a slight delay required release date Rear. We will still follow the commitments on transparency in the Java EE platform development process. Thus publicly announced target time to complete this work officially pushed back to the first half of 2017.
Java EE 7 release after two years, Oracle Java community to tell them it would go, and so on.When asked about the specific circumstances of the Java EE 8, Gierke said:
From a global perspective, Java EE 8 basically still continue to follow that Java EE 7 cliché story: participants continue to cling to other areas has been gradually not interested. In my opinion, this is because all major competitors have already begun turning their own cloud computing products (Oracle has Oracle Cloud, Red Hat has OpenShift, IBM has Bluemix, of course, there Pivotal Cloud Foundry).
JSR 372 and JSR 378 expert group members Josh Juneau talked about his views published in April 2016 blog post. After investigation, Juneau found by the non-Oracle specification managers control over Oracle JSR specification JSR managers control more active. JSR 372 is the number of submissions also decreased significantly (see figure below). Juneau think most of the work in October 2015 after all the Java community, mainly Arjan Tijms done, who is co-founder and development director Bauke Scholtz, and also the co-founder and chief ZEEF Web application experts.
InfoWorld contributing editor Paul Krill recently wrote an article mentioned, James Gosling found that Oracle's way of doing things people & ldquo; & rdquo ;: very uneasy
Oracle probably will not continue to provide much support for EE, but turn by communities ... to & ldquo; & rdquo ;, proprietary technology by & ldquo; Budget Motel & rdquo; mode of implementation of non-standard standards, & ldquo; customers only need to check-in, check-out is not required from & rdquo ;.
Spring 5 and Java EE
Krill released at JavaOne 2010 during a symposium on Java EE article describes about Spring and Java EE debate:
& Ldquo; I will never be confused with Spring and Java EE 6 because of overlap too much, & rdquo; As a consultant, author, and speaker Adam Bien said. In addition, he also mentioned that use both Spring and Java EE annotations can cause complex issues.
He said: & ldquo; For most projects, my personal opinion is that they will be treated differently, using Spring or Java EE 6 will do. & Rdquo; however, developers can also use the Spring tool in EE on the basis of 6, Bien said of.
But Caucho Technology's chief engineer Reza Rahman is more worried about the competition between the two technologies. & Ldquo; Java EE needs Spring, Spring also need as Java EE, & rdquo; Rahman said.
After about six years, the former Oracle Java EE evangelist and current consultant Gierke CapTech Ventures gave a Rahman similar view:
Spring and Java EE alleged relationship between competitive as the most important features. However, if carefully studied and soon you will find, once (and still current) synergies exist between the two, the relationship between them is not black and white, and a lot of gray area.
On the one hand, in some cases Spring-based Java EE specification is to build from, so if there is no Servlet API, it is difficult to imagine Spring MVC can be developed into its present form. On the other hand, the framework always the most important specification provides support.
Also note that, although the Spring dependent on Servlet API, but the initial release of Spring 5 does not include the new Servlet 4.0 API. This Gierke explains:
For us, Java EE 8 is the most important part is that Servlet 4.0 API and its support for the HTTP 2.0. This is somewhat predictable, but we finally released Spring 5 before everything is inconclusive, we are currently working with the most important implementer Servlet container (Tomcat, Jetty, Undertow) in close cooperation to ensure that the the first time they use the native API provides support for the implementation of HTTP 2.0.
Java community can do to turn things around?
Oracle in June 2015 published a blog post to help encourage the Java community:
Given these changes, you will have more time and opportunity to participate.
We will continue to encourage developers to track the JSR and JSR through various mailing lists and wiki, and try to download the reference implementation of Java EE 8 earlier version, etc. to provide feedback. We have seen a lot of people are interested in not only the function of Java EE 8, and has been involved in.
However, Krill in September 2015 published the article said, InfoWorld received mail from Oracle former senior employee, the message part summarized as follows:
Oracle is not interested in a competitor do the wedding dress, do not want to share their innovations.
The company is gradually abandoned Java EE (Enterprise Edition), but do not want others to continue to improve Java or Java EE, while also gradually neglected JCP (Java Community Process). & Ldquo; they have a kind of winner-take-all mentality, not interested in cooperation. & Rdquo;
This message is recommended JCP members to send an open letter to Oracle customers, warning them Java currently suffer treatment. Oracle never any & ldquo; Java Foundation & rdquo; to cooperate, is not prepared to open their own intellectual property rights.
In a recent article, Juneau explained Oracle necessary to promote the continued development of Jave EE should not give up the important reasons:
Obviously, in order to ensure security and guarantee to continue using the current API, these technologies need to continue to develop and improve. If someone simply wants to Java EE stand still, which means that all of some or all of the use of Java EE applications and services (probably a lot of things as we know it on the Internet) will be affected, we can not continue to develop in line with today's technology and safety requirements.
Gierke was pleased to see the community around Java EE 8 made many initiatives, but he also warned:
I think there is one aspect has not attracted enough attention to you, this problem is actually quite dangerous: this issue with us in the end be able to gather around the Java EE completely unrelated to how many members of the community, but because of licensing reasons for Oracle JSR we controlled almost helpless.
Oracle unless willing to take some legal action, otherwise the problem is completely no solution. I'm not sure whether people are willing to do so, someone had to Google this result we all know. So I suggest that you think the measures taken in case not feasible, it looks a little strange.
Java EE Guardian
After the early departure from Oracle, Rahman set up a Java EE Rise of the Guardians, intended to promote the continued development of Java EE, in particular:
To promote its Java EE 8.
It provides support for Java EE 8 JSR.
Lobbying Oracle commitments related to Java EE 8's.
We managed to arrest Oracle JSR resale to other suppliers.
Rise of the Guardians evidence Java EE provides no proof of progress in the Oracle Java EE development 8, and encourages the Java community to sign a petition, the petition will be submitted to Larry Ellison. InfoQ before publishing articles on the topic also for a lengthy discussion.
As a summary of the relevant Java EE 8 Oracle lost interest in doing, Gierke expressed his thoughts:
If this matter is not so far-reaching impact or severe, you may feel the current situation is somewhat ironic: Spring stack previously regarded as proprietary, because the development of the technology only to give a firm support. In some people the idea seems optimistic, Java EE stack is always completely open and community-driven. Now just because a company lost interest in Java, the whole Java world turned upside down.
This article Translator: Dayu if Chi