Simplified web module migration and new features for InstantOn rapid startup in 25.0.0.1
The 25.0.0.1 release expands the collection of features that you can use with InstantOn rapid startup and introduces a configuration option to simplify web module migration from other Java runtimes to Liberty.
In Open Liberty 25.0.0.1:
View the list of fixed bugs in 25.0.0.1.
Check out previous Open Liberty GA release blog posts.
InstantOn support for Batch and Connectors Inbound Security features
Open Liberty InstantOn provides fast startup times for MicroProfile and Jakarta EE applications. InstantOn supports a subset of Open Liberty features. As of the 25.0.0.1 release, the following features are enhanced to support InstantOn:
-
Batch API (
batch-1.0
) -
Jakarta Batch 2.0 (
batch-2.0
) -
Jakarta Batch 2.1 (
batch-2.1
) -
Java Connector Architecture Security Inflow 1.0 (
jcaInboundSecurity-1.0
) -
Jakarta Connectors Inbound Security 2.0 (
connectorsInboundSecurity-2.0
)
This enhancement enables you to rapidly deploy applications that use these features by using Open Liberty InstantOn. For more information, see Faster startup for containerized applications with Open Liberty InstantOn.
Configure the web module class loader for an enterprise application
Web modules (WARs) that are part of an enterprise application (EAR) can specify their own Class-Path. By default, Liberty adds the JARs that are referenced by a web module Class-Path
attribute to the web module class loader. However, some runtime implementations of Java EE and Jakarta EE instead use the enterprise application class loader for these JARs. Typically, the enterprise application class loader is the parent class loader for the web module class loader.
To enable smooth migration from such runtimes to Liberty, the 25.0.0.1 release introduces the webModuleClassPathLoader
configuration attribute for the enterpriseApplication
element, which controls what class loader is used for the JARs that are referenced by a web module Class-Path
attribute.
The default value for the webModuleClassPathLoader
attribute is war
. The war
value configures the web module Class-Path
to be loaded by the web module class loader. You can set the webModuleClassPathLoader
attribute value to ear
to configure the enterprise application class loader to load the web module Class-Path
.
For example, to configure an EAR file named myApp.ear
to use the ear
class loader, set the following Liberty configuration in the server.xml
file:
<enterpriseApplication location="myApp.ear" webModuleClassPathLoader="ear"/>
Develop and run your apps using 25.0.0.1
If you’re using Maven, include the following in your pom.xml
file:
<plugin>
<groupId>io.openliberty.tools</groupId>
<artifactId>liberty-maven-plugin</artifactId>
<version>3.11.2</version>
</plugin>
Or for Gradle, include the following in your build.gradle
file:
buildscript {
repositories {
mavenCentral()
}
dependencies {
classpath 'io.openliberty.tools:liberty-gradle-plugin:3.9.2'
}
}
apply plugin: 'liberty'
Or if you’re using container images:
FROM icr.io/appcafe/open-liberty
Or take a look at our Downloads page.
If you’re using IntelliJ IDEA, Visual Studio Code or Eclipse IDE, you can also take advantage of our open source Liberty developer tools to enable effective development, testing, debugging and application management all from within your IDE.
Get Open Liberty 25.0.0.1 now
Available through Maven, Gradle, Docker, and as a downloadable archive.