5.10.0

Last published : Aug 10, 2026
Related information

Overview of 5.10.0

This release contains the following notable changes:
  • Changes to application server support to modernize the architecture and address security vulnerabilities.
  • Important changes to supported environments. For details, read the Changes to supported environments section.
Attention:
Before upgrading an existing environment, read the Version upgrade section carefully.

Application servers

EBX® now supports Jakarta EE 10 or above. This change requires upgrades to several third party libraries, including Servlet 6.0 or greater, JSP 3.1 or greater, JMS 3.1 or greater, and Mail 2.1 or greater. See the links below for more information on requirements for specific components:
See Module development, Supported application servers, Java Message Service (JMS), JMS for distributed data delivery (D3), Installation notes and WebLogic AS support for more information.

Java compile-time environment

EBX® source code is now compiled with JDK 17, and the Javadoc is generated with JDK 17. JRE 11 and 8 are no longer compatible. We recommend that you upgrade your JDK to a recent LTS version.
See Supported application servers for more information.

JVM support

EBX® now supports JRE 21 LTS and JRE 25 LTS.
Note:
We recommend that you upgrade your JRE to Java 25 LTS version to take advantage of its performance improvements.

Version upgrade

In addition to the information in this release note, 5.10 Java API changes provides the complete list of the Java API changes in this release.

Changes to supported environments

The Supported environments chapter has been updated to include the following required changes:
Browser support
Microsoft Internet Explorer 8 and 9 are no longer supported.
For Mozilla Firefox, the support of ESR 52 has shifted to ESR 60.
JVM support
Starting with EBX® version 5.10.0 and later, you can use JRE 25. Use of one of the following Java Runtime Environment is required: JRE 17 LTS, JRE 21 LTS, or JRE 25 LTS.
Supported databases
Backward compatibility - SAP HANA as a back-end database engine for EBX® is discontinued as of this release; the inter-database migration provides a way to export the full content of a repository to another database.
Oracle 21c (Innovative Release) is no longer supported; the required version for Oracle is now 19c or 23c.
Minimum supported version of PostgreSQL is now 14.
Minimum supported version of Microsoft SQL Server is now 2016.
See Inter-database migration for more information.
Tomcat 11 support
Minimum supported version of Tomcat 11 is now 11.0.8.
WebLogic AS support
Currently, no version of WebLogic AS supports Jakarta EE 10. Please be aware that, according to Oracle's Statement of Direction, future WebLogic AS 26 might be compatible with EBX®.
See The Future of WebLogic Server and Coherence: Jakarta EE 11, JDK 25, and Version 26 for more information.

Backward compatibility

Module development
Developers of EBX® 5.10.0 onwards should be aware that, as a result of the move from Java EE to Jakarta EE, the primary package name for all implemented APIs has changed from javax.* to jakarta.*. This will almost certainly require code changes to enable modules or other libraries. An important point is to consider this migration as the first step toward compatibility with EBX® 6.2.x and later.

How to upgrade an installed environment

To upgrade EBX®, perform the following steps:
  1. Back up your repository, including the RDBMS and the ebx.repository.directory directory.
  2. Replace the *.war and ebx.jar files on your application server.
  3. Add the new required ebx-ui.war file in your EAR or on your application server. See Java EE deployment for more information.
  4. Add the new main logging category, in the ebx.properties file ,with the ebx.log4j.category.log.restServices property key. See Configuring the EBX® logs for more information.
Attention:
Java types in ebx.jar are no longer obfuscated.
If using the EBX® add-ons, make sure that the version of the add-ons is compatible with EBX® version 5.10 before upgrading. For the backward compatibility of the add-ons themselves, refer to the release note of each add-on.
Once an EBX® repository has been used with this version, using it with a previous version is not supported. Consequently, a backup must be created before upgrading, as described above, in order to maintain the possibility of downgrading later.

5.10.0 Closed issues

Core Engine

  • CP-28405 An XML parsing exception occurs when using JRE 23 or newer.
  • CP-28732 A 'Wizard is disabled' log entry displays when accessing the UI.
    This occurs when the property ebx.install.enabled is set to true and the license has expired.

Data Services

  • CP-27988 The FastClasspathScanner code should be migrated to ClassGraph.
  • CP-29812 The REST Toolkit service might not blocked even if the EBX® repository is not yet installed.

Distributed Data Delivery

  • CP-28538 Data services operations in D3 replica nodes may fail during broadcast.

Documentation

  • CP-28780 The documentation should declare that setting Tomcat's unpackWARS to false is not supported.

User Interface

  • CP-29408 User services that use UserServiceRecordFormFactory are missing concurrent change detection.