The Red Hat JBoss Enterprise Application Platform 8.1 Beta release is now available, continuing our commitment to supporting and modernizing enterprise Java applications across a wide range of deployment environments.
Whether running on traditional infrastructure like bare metal and virtual machines or embracing cloud-native architectures, this release brings enhanced capabilities to help organizations build, run, and scale Java applications with confidence.
This post highlights new features in JBoss EAP 8.1 Beta release that streamline your Java application deployments for faster startup times, more consistent deployments, and improved portability. For a full list of features and capabilities, read the JBoss EAP 8.1 beta release notes.
Bootable JARs
Bootable JARs provide the convenience of modern microservice packaging to enterprise Java, coupled with the robustness of the JBoss EAP platform. Bootable JARs are self-contained, executable artifacts that package both your application and the JBoss EAP runtime into a single JAR file. This enables a simplified deployment model, similar to Spring Boot, while maintaining enterprise-grade capabilities and compliance.
For developers, bootable JARs make it easier to build, test, and deploy Java EE applications with fewer moving parts. They can use familiar Maven workflows to generate these JARs, streamlining CI/CD pipelines and reducing environment drift between development and production.
From an architectural perspective, bootable JARs support faster startup times, more consistent deployments, and improved portability across cloud, container, and on-premises environments. This results in better developer productivity and a more resilient, responsive experience for end users.
Learn more: The bootable JAR (JBoss EAP documentation)
Server footprint trimming
Galleon brings fine-grained control and modernization to traditional Java application deployments on both bare metal and virtual machines.
Galleon layers in JBoss EAP provide a flexible way to provision customized, lightweight server runtimes tailored to your application’s needs. Instead of deploying the full JBoss EAP distribution, you can use Galleon to include only the necessary subsystems and features. This reduces footprint, startup time, and attack surface.
This approach is especially valuable when deploying to bare metal or virtual machines, where resource optimization, boot time, and consistency across environments are critical. Galleon lets you define your runtime as code, enabling repeatable builds and streamlined DevOps workflows without unnecessary bloat.
Learn more: Build & deploy JBoss EAP 8 images in OpenShift with Galleon & Helm charts
Video demo: Modernize Jakarta EE with JBoss EAP provisioning
The following video demonstrates trimming and bootable JARs with JBoss EAP.
Migrate to JBoss EAP 8
Download JBoss EAP 8.1 today. Our migration guide has the information you need to make a seamless transition.
If you're planning a larger migration, be sure to check out our JBoss EAP 7 to 8 checklist for a more structured approach.
Migration toolkit
Red Hat's migration toolkit for applications simplifies and accelerates Java application migrations by identifying issues and offering actionable guidance, making transitions to platforms like JBoss EAP 8 more efficient and low-risk.
JBoss EAP 8 support lifecycle
Refer to the following table for the lifecycle dates for all currently supported Red Hat Application Services products.
Version | Tier | General availability | Full support ends | Maintenance support ends | Extended life cycle support (ELS) 1 ends | Extended life cycle support (ELS) 1 ends |
---|---|---|---|---|---|---|
Full support | ||||||
8.x | N/A | February 5, 2024 | February 5, 2028 | February 5, 2031 | February 5, 2033 | February 5, 2034 |
Maintenance support | ||||||
7.x | N/A | May 1, 2016 | December 31, 2023 | June 30, 2025 | October 31, 2027 | October 31, 2030 |
Extended support | ||||||
6.x | N/A | June 1, 2012 | June 30, 2016 | June 30, 2019 | June 30, 2022 | December 30, 2028 |