BT

Facilitating the spread of knowledge and innovation in professional software development

Contribute

Topics

Choose your language

InfoQ Homepage Jakarta EE Content on InfoQ

  • OpenLiberty Moves to Four-Week Releases

    OpenLiberty, the project behind IBM WebSphere, has released version 19.0.0.1 as its first move into four-week releases.

  • Spring Boot 2.2 Reaches First Milestone Release with Performance and Memory Improvements

    The Spring Boot team recently released v2.2.0 M1, the first milestone release of Spring Boot 2.2. It includes performance and memory improvements, Kubernetes-detection, and third-party library updates. Over 140 issues were resolved with this release. Starting with this release, JMX is now disabled by default.

  • MicroProfile Community Launches MicroProfile Starter, a Web-Based Project Generator

    The MicroProfile community has recently launched a beta release of MicroProfile Starter, a website that allows you to create, configure and download a new automatically generated project. Users can specify the project's coordinates (groupId and artifactId), which version of MicroProfile they'd like to use, their MicroProfile server, and a number of other project configuration options.

  • Eclipse Releases GlassFish 5.1 Certified as Compatible with Java EE 8

    Eclipse has achieved another GlassFish milestone with the anticipated GA release of version 5.1. A year in the making, this milestone included previous GlassFish milestones such as the full migration of source code and open-sourcing the Java EE TCK (September 2018), the RC1 release of GlassFish 5.1 (October 2018), and the integration of EclipseLink and Eclipse Jersey in GlassFish (December 2018).

  • RedHat Releases JBoss 7.2 With EE 8

    RedHat has released JBoss 7.2, with full support for the EE 8 specification. This release brings another application server into the Jakarta EE, post-Oracle environment. It also provides support for modern web technologies such as Servlet 4.0 with HTTP/2 capabilities.

  • A New Era for GlassFish: Source Code Migrated, and the Java EE TCK Released as Open Source

    The Eclipse Foundation recently announced two milestones in September 2018: the migration of GlassFish source code from Oracle has been completed; and the Java EE TCK is now open-sourced. Considered a major milestone for the advancement of Jakarta EE and a new era for GlassFish, “this is another step in making Jakarta EE a vehicle for innovation in cloud-native application development.”

  • Eclipse Releases Versions 1.4 and 2.0 of MicroProfile

    The Eclipse Foundation recently released versions 1.4 and 2.0 of MicroProfile featuring relevant updates to the APIs, including comprehensive Test Compatibility Kits (TCKs), Maven coordinates, Javadocs, and Git tags. These versions are fully aligned with Java EE 7 and Java EE 8. The synergies between MicroProfile and Jakarta EE have sparked some speculation that the two platforms could merge.

  • The MicroProfile Community Influence on Jakarta EE

    James Roper, senior developer and co-creator of the Lagom microservices framework at Lightbend, was recently named a committer for Eclipse MicroProfile. As the first committer to represent Lightbend, Roper shared his journey and the MicroProfile community influence on Jakarta EE. InfoQ spoke to Roper about his experiences and reached out to fellow MicroProfile committers for their input.

  • Cloud Native Java Has A New Home: Jakarta EE

    Mike Milinkovich, executive director at the Eclipse Foundation, introduced a new Eclipse governance model and roadmap for Jakarta EE at this year’s JAX conference. Based on a recent survey of over 1800 Java developers, the new governance model will focus on support for cloud native application development and faster release cycles. Milinkovich spoke with InfoQ on the future of Jakarta EE.

  • Jakarta EE Working Group Established

    Future versions of the Java EE technology will be branded as Jakarta EE, and it’s currently under active development at the Eclipse Foundation. When Java EE was under Oracle’s stewardship, it used the JCP to make decisions and introduce new features. Since there’s no JCP for Java EE at Eclipse, a new process had to be established. That process is now called the Jakarta EE Working Group.

  • Java EE Guardians Moving Forward with Jakarta EE

    Shortly after Java EE was rebranded to Jakarta EE, well-known Java EE evangelist Reza Rahman recently closed the change.org petition to declare victory in the original petition filed by the Java EE Guardians almost two years ago, in which they encouraged Oracle to move forward with Java EE 8. Rahman spoke to InfoQ about the future of the Java EE Guardians and Jakarta EE.

BT