BT

InfoQ Homepage Java EE Content on InfoQ

  • Apache Releases TomEE 7.1 with Support for Java 8 and MicroProfile 1.2

    The Apache TomEE community has released TomEE 7.1, a significant upgrade featuring support for Java SE 8 and MicroProfile 1.2. TomEE 7.1 serves as a gateway release for TomEE 8 that will be compliant with Java EE 8/JakartaEE and MicroProfile 1.3. David Blevins, founder and CEO of Tomitribe, spoke to InfoQ about this latest release.

  • 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.

  • JBoss Web Server 5 with Tomcat 9 is Available

    Red Hat JBoss Web Server (JWS) combines the Apache web server with the Tomcat servlet engine for building, deploying, and maintaining web applications and large-scale websites. JBoss Web Server version 5 was recently released supporting Tomcat 9 and introduces several new features and enhancements.

  • 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.

  • Q&A with Bob McWhirter on WildFly Swarm Rename to Thorntail

    In early 2015, Red Hat released Wildfly Swarm, which allows Java EE based applications to run as microservices. The approach allowed developers to migrate Java EE monolith applications to microservices by creating an uber-JAR that not only contains the Java program but embeds its dependencies as well. Wildfly Swarm was recently renamed to Thorntail. 

  • 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.

  • Java EE Becomes Jakarta EE

    After Oracle expressed its desire that Java EE be rebranded as part of the project's transfer to Eclipse, the community has voted, and the new name for Java EE going forward will be Jakarta EE. Mike Milinkovich, executive director of the Eclipse Foundation, wrote in a blog post that almost 7,000 people voted in the community poll, with over 64% choosing "Jakarta EE".

  • From Java EE to Jakarta EE: the Java EE Guardians Rebranding Debate with Oracle

    Frustrated with the lack of response from Oracle, the Java EE Guardians recently submitted an open letter to Oracle expressing their concerns on the rebranding of Java EE. Despite the efforts and data collection by the Java EE Guardians, the rebranding of Java EE will move forward.

  • Eclipse MicroProfile 1.3 Is Now Available

    Eclipse MicroProfile extends Java EE to better address microservices by providing an open-source community specification for enterprise Java microservices. Release 1.3 introduces the OpenAPI, OpenTracing, and Rest Client APIs and updates the Config and Metrics APIs.

  • Vote for Java EE's New Name

    The quest to rename Java EE has reached the final phase, with the community being asked to vote for one of two final possibilities.

  • Public Review of Java MVC 1.0 Specification is Now Open

    Public review of JSR-371, Model-View-Controller (MVC) version 1.0 specification, is now open. The latest features include support for data binding and internationalization. Eclipse Ozark, a full implementation of MVC 1.0, is expected to release version 1.0 in conjunction with the final release of JSR-371. Ivar Grimstad, principal consultant for the Cybercom Group, spoke to InfoQ about MVC 1.0.

  • No JCP for Java EE

    Oracle does not support or recommend the use of the JCP (Java Community Process) for future Java EE enhancements. "Oracle recommends and supports the use of EE4J-driven processes for functional enhancements to Java EE 8 specifications, and does not recommend or support use the JCP process for any future Java EE 8 functional enhancements."

BT

Is your profile up-to-date? Please take a moment to review and update.

Note: If updating/changing your email, a validation request will be sent

Company name:
Company role:
Company size:
Country/Zone:
State/Province/Region:
You will be sent an email to validate the new email address. This pop-up will close itself in a few moments.