Language Selection

English French German Italian Portuguese Spanish

Java finally goes all in on open source with the Jakarta EE 8 release

Filed under
OSS

Java being fully open-sourced has been a long, long time coming. While Sun open-sourced some of Java as long ago as November 2006, actually using Java in an open-source way was… troublesome. Just ask Google about Android and Java. But for Java in the enterprise things have changed.

On September 10, The Eclipse Foundation announced the full open-source release of the Jakarta EE 8 Full Platform and Web Profile specifications and related Technology Compatibility Kits (TCKs).

This comes after Oracle let go of most of Java Enterprise Edition's (JEE) intellectual property. Oracle retains Java's trademarks though -- thus Java EE naming convention has been changed to Jakarta EE. But for practical programming and production purposes Jakarta EE 8 is the next generation of enterprise Java.

Read more

The Eclipse Foundation Releases Jakarta EE 8 Specifications

  • The Eclipse Foundation Releases Jakarta EE 8 Specifications; Completes Transition to Eclipse Foundation as the New Home for Open Source Cloud Native Java

    The Eclipse Foundation today announced during the JakartaOne Livestream virtual conference the release of the Jakarta EE 8 Full Platform and Web Profile specifications and related Technology Compatibility Kits (TCKs). This release provides a new baseline for the evolution and innovation of enterprise Java technologies under an open, vendor-neutral, community-driven process. As a result, Java vendors, developers, and customers alike now have a foundation for migrating mission-critical Java EE applications and workloads to a standard enterprise Java stack for a cloud native world. This release represents a major milestone for the world’s leading innovators in cloud native Java, including Fujitsu, IBM, Oracle, Payara, Red Hat, Tomitribe, and dedicated independent community members who are collaborating at the Eclipse Foundation to advance Jakarta EE, the successor to Java EE.

Authored by Sean Michael Kerner

Jakarta EE 8: The new era of Java EE explained

  • Jakarta EE 8: The new era of Java EE explained

    Java EE is a fantastic project. However, it was created in 1999, under the name of J2EE, and is 20 years old, which means it also faces challenges in keeping pace with enterprise demands.

    Now, Java EE has a new home and a new brand. The project was migrated from Oracle to the Eclipse Foundation, and it is called Jakarta EE, under the Eclipse Enterprise for Java (EE4J) project. The Eclipse Foundation released Jakarta EE 8 on September 10, and in this article, we’ll look at what that means for enterprise Java.

    Java EE was a very strong project that was widely used in many kinds of enterprise Java applications and many big frameworks, such as Spring and Struts. Developers may have questioned its features and evolving processes, but looking at its high usage and time in the market, its success is undeniable. Nonetheless, the enterprise world doesn’t stop, and new challenges emerge all the time. The speed of change has increased, with new technologies such as cloud computing being developed to provide better solutions, and Java EE needed to keep pace as well.

Hey, We're Open Source Again! Eclipse Unveils Jakarta EE 8

  • Hey, We're Open Source Again! Eclipse Unveils Jakarta EE 8

    The enterprise developers’ edition of Java has gone completely open source with a new version managed entirely by the Eclipse Foundation. The Foundation released Jakarta EE 8 with a flourish yesterday.

    Jakarta took a winding road to get to this point. Originally called J2EE when released in 1999, it was renamed to Java EE in 2006. Then, Oracle bought Sun three years later, which locked the product up in Fort Larry for the best part of a decade.

    Citing a wish to make things more open, it agreed to give Java EE back to the open source community in 2017, choosing the Eclipse Foundation. While it gave the Foundation the IP rights to the code, though, it held onto the name. So Eclipse had to find another one. Hence, Jakarta.

Jakarta EE now operates under open, community-driven process

  • Jakarta EE now operates under open, community-driven process

    After transitioning from Oracle to the Eclipse Foundation in 2017, Jakarta EE (previously known as Java EE), has reached another major milestone.

    With today’s release of the Jakarta EE 8 Full Platform and Web Profile specification, the project now has a new baseline for having an “open, vendor-neutral, community-driven process.” Now, Java vendors, developers, and consumers will have a foundation for migrating Java EE applications to a standard enterprise Java Stack.

More and the original

The Eclipse Foundation Wins Duke’s Choice Award

  • The Eclipse Foundation Wins Duke’s Choice Award for Open Source Contributions to the Java Ecosystem

    The Eclipse Foundation was awarded a Duke’s Choice Award yesterday in recognition for outstanding open source contributions to the Java ecosystem and the community-driven achievement of moving Java EE technologies from Oracle to the Jakarta EE Working Group. Held at the Oracle Code One conference and tradeshow, the Duke’s Choice Awards celebrate invaluable innovation in Java-based technologies and contributions to Java.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

today's howtos

Security Leftovers

  • Security updates for Monday

    Security updates have been issued by Debian (pillow, ruby-kramdown, wpa, and xrdp), Fedora (ark and rpki-client), Gentoo (apache, ark, global, gthumb, and iproute2), openSUSE (chromium, grub2, java-11-openjdk, libX11, and opera), Red Hat (bind, chromium-browser, java-1.7.1-ibm, java-1.8.0-ibm, and libvncserver), SUSE (LibVNCServer, perl-XML-Twig, thunderbird, and xen), and Ubuntu (samba).

  • Have I Been Pwned to release code base to the open source community

    Members of the general public can submit their email addresses into the Have I Been Pwned search engine to find out if they have been "pwned," and if their emails have been linked to a data breach, each one and a summary of what happened is displayed -- as well as what information has been exposed. Since its launch in 2013, Hunt has poured more resources, including time and energy, into managing the search engine over time, expanding the service to include domain monitoring and breach alerts. At the heart, one main operator isn't enough to ensure future scalability or sustainability, and with this in mind, Hunt previously attempted to find a buyer to help expand his life's work. Unfortunately, the merger and/or acquisition process failed, and so Hunt has decided to pursue another alternative -- opening up the Have I Been Pwned code base to the open source community.

  • Researcher Demonstrates Several Zoom Vulnerabilities at DEF CON 28

    Popular video conferencing app Zoom has addressed several security vulnerabilities, two of which affect its Linux client that could have allowed an attacker with access to a compromised system to read and exfiltrate Zoom user data—and even run stealthy malware as a sub-process of a trusted application. According to cybersecurity researcher Mazin Ahmed, who presented his findings at DEF CON 2020 yesterday, the company also left a misconfigured development instance exposed that wasn't updated since September 2019, indicating the server could be susceptible to flaws that were left unpatched.

Red Hat/Fedora Leftovers

  • Fedora Nest 2020

    This year Flock did not happen due to COVID-19, and in its place, Fedora Nest happened. After many events I’ve seen going virtual in the last few months, I was skeptical. I was yet to see an acceptable online platform to run events. I was wrong on the platform. Fedora Nest used Hopin , which is by far the best platform for events I’ve seen so far. Don’t get your expectations too high, though, because when I say the best one I’ve seen so far, only means that it is usable, and it does not mean in any way that is on par of real conferences. I might be a weird being, but I find traveling relaxing, so I usually add to the joy of the conference the pleasure of traveling. In addition to this, at conferences, I find myself to connect with people - sometimes briefly, sometimes more deeply - and this does not occur in online events. For those reasons, I really hope we will be able to soon go back to in-person conferences.

  • Miroslav Suchý: Nest 2020 - my notes

    This year, we had Nest conference instead of traditional Flock, which has been canceled due to COVID. The conference happened purely remotely over the Hopin video conference. This was good and bad. The good is that we saved a lot on traveling and that it happened at all. It would be bad if it was canceled. The bad part was that I found it hard to focus on the conference. There are too many distractions at home. It was much harder to socialize. And a lot of people had issues either with microphone or internet upload. It was sometimes hard to follow. The conference was organized mostly for US folks, and therefore some sessions were very late in my timezone.

  • Btrfs by default status updates, 2020-08-09
  • Fedora Btrfs Activity Continues - New Options To Control Discard, Compression

    Fedora developers continue embracing the work on making the Btrfs file-system the default for F33 desktop variants. Their latest progress report indicates new installation options being wired up for the Btrfs support. A new Anaconda Kickstart install configuration knob is being added for setting the async discard behavior for solid-state drives. This configuration option will simply set the Btrfs DISCARD option to be enabled by default per the /etc/fstab options. They are still weighing whether to make it the default or more than likely that default transition would be next year for Fedora 34.

  • “To be, or not to be,” vulnerable… How customers and partners can understand and track Red Hat security vulnerabilities

    That is the question. Yes, I believe William Shakespeare was thinking about container security when he began Act 3 of Hamlet. He probably scanned his Red Hat Universal Base Image (UBI) 8 container with multiple vulnerability scanners, and with "the heart-ache and the thousand natural shocks", noticed each report told him something different. One report said his container had a vulnerability, another indicated the vulnerability was patched, and another didn’t even show the vulnerability. As Hamlet contemplates his fate, it’s no wonder he says: "With this regard their currents turn awry, And lose the name of action." In other words, he rips up the reports and does nothing! In many ways our customers are experiencing the same vulnerability inconsistencies as Hamlet. But unlike our hero’s tragic fate, there is some good news: Red Hat is working with independent software vendors (ISVs) to help drive vulnerability consistency for both Red Hat and our partners.

  • Kubernetes and the hybrid cloud with Skupper

    DevNation Tech Talks are hosted by the Red Hat technologists who create our products. These sessions include real solutions plus code and sample projects to help you get started. In this talk, you’ll learn about Kubernetes and the hybrid cloud with Skupper from Ted Ross and Burr Sutter.

today's howtos