Introduction Now that Jakarta EE 8 has been released, several runtimes have been updated to support Jakarta EE 8. To showcase this, I’ve written the bare minimum required to deploy a Jakarta EE application onto any Jakarta EE compliant server (in this instance IBM’s Open Liberty. pom.xml The majority of the code is the Maven pom.xml file as shown below. <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>com.developinjava</groupId> <artifactId>simple</artifactId> <version>0.0.1-SNAPSHOT</version> <packaging>war</packaging> <properties> <failOnMissingWebXml>false</failOnMissingWebXml> <maven.

Introduction WildFly Swarm applications can be deployed to Heroku, simply by adding a few files to the deployment. In this post, I’ll show the changes that are needed to be made to a WildFly Swarm application and how to then deploy the application to Heroku. I’ll show how to deploy my Fruits example WildFly Swarm application to Heroku. The source for this application can be cloned from GitHub at https://github.

Introduction There are many different frameworks that allow you to develop and deploy microservices. Payara, the team behind the Payara Server have a couple of options for deploying microservices - PayaraMicro and Payara MicroProfile. So, what exactly are PayaraMicro and Payara MicroProfile? What is Payara Micro? Both PayaraMicro and Payara Microprofile are small .jar files that allow you to deploy .war files from the command line allowing Java EE applications to be easily executed.