Migrating from 13.1 to 13.2
Upgrade to 13.2 is only supported from an Axon Ivy Engine 10.0 and higher. If you have an Axon Ivy Engine older than version 10.0 you need to first migrate to a version between 10.0 and 12.0.
Persistence API (Hibernate)
We migrated the Persistence API from Java Persistence API (JPA) version 2.2 to Jakarta Persistence API version 3.2. The implementation of the API was migrated from Hibernate 5.6 to 7.0.
The package of the new version has changed from javax.persistence to jakarta.persistence.
The code of Ivy projects needs to adapt to this change.
Use find and replace in files in the Designer to migrate your project.
HttpHeaderSecurityFilter and RemoteIpFilter in web.xml
We now allow to define the Reverse Proxy HTTP Headers and security response HTTP Headers via the ivy.yaml. Even if it is still possible to define this things via the web.xml you should no longer do that, otherwise the header maybe appear twice. So you should remove the following configurations and make the adjustments in the ivy.yaml:
org.apache.catalina.filters.HttpHeaderSecurityFilter→WebServer.HttpHeadersorg.apache.catalina.filters.RemoteIpFilter→ReverseProxy.HttpHeaders
Schema header in ivy.yaml and app.yaml
If your ivy.yaml and app.yaml has no schema header specified, the Axon Ivy Engine will now automatically assume that these files are in the latest version and will no longer auto migrate them. We suggest that you always version your file with a schema header.
Tag Legend:
This migration is handled by the Migration Wizard.
This migration will change something in the engine operation. If you are responsible for the operation of an engine, check if this change affects you.
This migration highlights behaviors or features that are deprecated. That functionality will be removed soon. If you are responsible for the operation of an engine, you should check if this change affects you.
This migration will remove a behavior or feature that has been available for the engine operation. If you are responsible for the operation of an engine, check if this change affects you.
This migration is handled by the Project Conversion automatically.
This migration will change a certain behavior in the projects. If you are a project developer, check if this change affects you.
This migration will mark features or APIs as deprecated in projects. That functionality will be removed soon. If you are a project developer, check if this change affects you.
This migration will remove a behavior or feature of a project. If you are a project developer, check if this change affects you.