Retirement Notice Originally Published: May 27, 2026
Retirement Notice Revised - May 28, 2026: Corrected a typo in the contact@onebx.com email address

May 27, 2026

Support for EBX 6.2.0, 6.1.x (from 6.1.0 to 6.1.5), 5.9.26 and below will end on May 31, 2027.
This retirement will also apply to the compatible EBX Add-On packages for these versions.
During the next 12 months, Support will answer product questions, but no new defect corrections, in the form of hotfixes or service packs, will be provided for these versions.

Why Are We Ending Support for EBX 6.1.x ?

EBX 6.1.0 was released in March 2023.

Security — the primary driver

Critical third-party libraries used by EBX — including Spring — no longer provide security patches for versions that are not compliant with the Jakarta EE framework. EBX 6.1.x falls into this category. Continuing to run on 6.1.x means customers will no longer receive security fixes for these components, creating an increasing exposure over time.

Performance and storage improvements

EBX 6.2.x versions deliver significant improvements over 6.1.x, particularly regarding Lucene index management:

• Faster index build and recovery
• Reduced disk usage by Lucene indexes
• Lower memory consumption
• Reduced database size

Why Are We Ending Support for EBX 6.2.0 ?

EBX 6.2.0 was released in June 2024. It introduced Jakarta EE compatibility and initial improvements to Lucene index management. However, versions 6.2.1, 6.2.2, and 6.2.3 have significantly raised the bar. Customers remaining on 6.2.0 are missing substantial improvements :

• Stability and bug fixes — critical corrections delivered across 6.2.1, 6.2.2, and 6.2.3
• Massive storage reductions
• Memory optimizations
• Indexing speed and reduced index size
• Faster initialization
• Improved Validation Framework performance
• Faster imports and replication
• Workflow enhancements

Versions 6.2.1 and above are more mature, more stable, and functionally richer. We strongly recommend customers move to the latest available 6.2.x release.

What’s Coming

For customers on the EBX 5.9.x branch

EBX 5.9.27 remains supported but will no longer receive functional enhancements nor security patches.

For customers who wish to stay on the 5.9.x branch while benefiting from a more secure foundation, we are planning EBX 5.10 in 2026.
This release will introduce Jakarta EE compatibility and include a major update of third-party components — directly addressing the security concerns described above.

For customers on the EBX 6.2.x branch

We are planning EBX 6.2.4 in 2026. As part of our ongoing modernization, we are evaluating compilation with JDK 21. While this remains a recommendation at this stage, customers are encouraged to begin assessing their environments for JDK 21 compatibility ahead of this release.

Upgrade Paths

Upgrading from EBX 6.2.0

Upgrading from 6.2.0 to the latest 6.2.x release is a straightforward process. Since 6.2.0 already introduced Jakarta EE compatibility, there are no framework-level changes required. Customers can upgrade directly without any specific development effort.

Upgrading from EBX 6.1.5

Upgrading from 6.1.5 involves migrating to the Jakarta EE framework. The development
changes themselves are limited and largely mechanical:

• Namespace renaming — Java EE package names (e.g. javax.* ) must be renamed to
  their Jakarta equivalents (e.g. jakarta.* ).
• Third-party library updates — any library your application depends on must be upgraded
  to a version compatible with Jakarta EE.
• Application server — the target application server must itself support Jakarta EE. Ensure
  your runtime environment (Tomcat, WildFly, or equivalent) meets this requirement before
  starting the migration.

In practice, the main effort lies in testing : validating that the updated libraries and renamed namespaces do not introduce regressions in your custom code and integrations. Plan your migration timeline accordingly.

If you need assistance planning or executing your upgrade project, our team is available to help, please reach out at contact@onebx.com.

Conclusion

Upgrading to a supported version of EBX is first and foremost a security decision. As key third-party components restrict security updates to Jakarta EE-compliant environments, remaining on
EBX 6.1.x or 6.2.0 creates an increasing risk exposure that we cannot remediate on older versions.

Beyond security, the improvements delivered since 6.2.1 — in stability, performance, and functionality — make the upgrade a clear benefit for all customers. We are committed to supporting this transition and will provide guidance and resources to help customers move to a current, secure, and fully supported version.

Finally, for customers who require additional time before completing their upgrade, extended support options may be available. Please contact your account owner to discuss your situation and the options that may apply to you.

As we continue to evolve the EBX® platform, ending support for versions 6.2.0, 6.1.x, 5.9.26 and below is a necessary step driven primarily by security considerations.
Third-party libraries that EBX depends on are increasingly restricting security updates to Jakarta EE-compliant environments only.
Remaining on unsupported versions exposes customers to unpatched vulnerabilities.
Beyond security, versions 6.2.1 and above deliver substantial improvements in stability, performance, and functionality that customers will directly benefit from.

Those versions will be retired on May 31, 2027.