title

WebLogic 15c Compatibility Platform

As Liferay continues to invest in platform flexibility and enterprise stability, empowered by Jakarta EE, we are pleased to share that DXP is now certified for use with Oracle WebLogic Server 15c. This application server will be fully supported for Enterprise tier customers. Additionally, to empower DXP deployment on Oracle’s server, we have released a dedicated DXP WAR file optimized for WebLogic 15.

Key Benefits:

Modernized Tech Stack: Provides compatibility with the latest release from Oracle, ensuring your infrastructure is ready for the next generation of enterprise Java applications.
Simplified Installation: Streamlined deployment provided through the dedicated Weblogic WAR file.
Security Compliance: Moving to WebLogic 15c ensures you stay ahead of the security and patch lifecycles of older, non-Jakarta-based application servers.

LPD-44582 - Weblogic 15.1.1 Support

Generally Available (aka OOTB)

Compatibility Matrix Expanded Platform

Platform flexibility and enterprise system support is important to our users. With this release we have expanded the Compatibility Matrix to include some new environments.

Application Servers:

Added support for WebLogic 15c (see details in dedicated WebLogic 15 release note)
Expanded Jboss version support from 8.0 to 8.x to help our users stay up to date with Red Hat support policy

Databases:

Added support for MariaDB 11.8
Added support for PostgreSQL 17.x

Operating Systems:

Added support for Red Hat Enterprise Linux 10

Key Benefits:

Access to newer versions of environment to ensure the latest performance, compliance, and security patching access.

LPD-79566 - 2026.Q1 Compat Matrix Expansion

Generally Available (aka OOTB)

Liferay Faces (JSF) for Jakarta Platform

Liferay has released a new version of the Liferay Faces (JSF) portlet bridge framework that is now compatible Jakarta EE, allowing users to migrated JSF portlets for usage with 2026.Q1.

Key Benefits:

Jakarta Support: JSF portlets can now be used on DXP with Jakarta namespace.
Simplified Migration: Liferay continues to support JSF 2.3-built portlets to make it easy to migrate to Jakarta with minimal breaking changes.
PrimeFaces support: Liferay has enabled usage of PrimeFaces portlets with Liferay DXP.

LPD-74294 - Upgrade faces repositories to Jakarta

Generally Available (aka OOTB)

AI Rules Files for Liferay Workspace Integration

AI Rules Files (.workspace-rules) are now available OOTB with new Liferay Workspaces. These files provide AI agents with the Liferay-specific logic, context, and guardrails needed to generate accurate, best-practice customizations for Liferay DXP. These rules are symlinked for automatic discovery by Claude Code, Cursor, Gemini, GitHub Copilot, and Windsurf.

Blade 8.0 or higher is required to automatically set up new Liferay Workspaces with the AI Rules Files.

Key Benefits:

Allows AI agents to become aware of the structure of Liferay Workspaces without any manual configuration.
Assists new users with setting up a Liferay Workspace and running Tomcat bundle, with explanations for commonly used Blade commands.
Provides Liferay recommended best practices for development.
Enables AI agents to access the Liferay MCP server to query content, manage objects, and execute actions within the portal.
Guided experience available to create and deploy a sample Client Extension, allowing users to quickly see Client Extensions in action in a running portal instance.

LPD-74926 - [MVP] Context Files for Workspace

AI Tools in Workspace

Generally Available (aka OOTB)

Integration Test BOM Integration

In order to run integration tests locally, customers previously had to manually identify and set the correct test dependency versions for their corresponding Liferay version in build.gradle, which was a tedious and error prone process. We now provide a dedicated Integration Test Bill of Materials (BOM) file, release.dxp.bom.test, that automatically provides the correct test dependency versions and is included by default with Liferay Workspaces.

Key Benefits:

Liferay Workspaces will automatically pull in the integration test BOM.
Customers can omit the versions when declaring test dependencies in build.gradle, the integration test BOM will provide the correct versions automatically for their Liferay version.
- Previous: testIntegrationImplementation group: "com.liferay.portal", name: "com.liferay.portal.test", version: "24.5.1"
- Now: testIntegrationImplementation group: "com.liferay.portal", name: "com.liferay.portal.test"

LPD-52131 - Integration Test BOM

Generally Available (aka OOTB)

Code Upgrade Tool Integration

In order to assist customers with upgrades to newer Liferay versions, Blade and Workspace users now have a dedicated gradle command upgradeSourceCode to migrate their code automatically to their desired Liferay version. This will do in-place updates to custom code to account for breaking changes in the latest Liferay version.

For customers migrating to Jakarta for the first time, the Jakarta Migration Tool upgradeJakarta is also available to automatically convert their source code from Java EE to Jakarta EE for DXP-provided libraries. The Code Upgrade Tool should be executed first before running the Jakarta Migration Tool.

Key Benefits:

This tool simplifies the process for users migrating their code to newer Liferay versions, providing:

Automatic source code migration for projects to a target Liferay version.
Liferay version specific code upgrade automations to account for breaking changes.
Integration with Liferay Workspace.

LPD-66652 - Make upgrade sf command discoverable

Generally Available (aka OOTB)

Allow Removing FDS Management Bar in Empty State Low/No-Code

This feature introduces a cleaner, more flexible empty-state experience in the Frontend Data Set by allowing the search bar and management bar to be hidden when no content is present.

Key Benefits:

The Dataset Consumer is able to hide Data Set management bar by just clicking a toggle
If toggle is enabled, management bar won’t be rendered in case of a “real” empty state
This can be configured both in system and custom datasets

LPD-47847 - Allow Removing FDS Management Bar in Empty State

Managing Data Sets

Release Flag (opt-in)

Enable end-users to have User Views in the Frontend Data Set Low/No-Code

This feature introduces User Views in Frontend Data Sets, allowing end users to personalize how data is displayed by saving and reusing their preferred filters, sorting, and visualization mode across the platform.

Key Benefits:

Users can easily create and switch between custom views tailored to their needs
Personalized views can be saved and reused, improving productivity and consistency
Administrators can control whether Custom Views are available per Data Set