diff --git a/java/migration.md b/java/migration.md index 7d6b4d281d..286c6ff272 100644 --- a/java/migration.md +++ b/java/migration.md @@ -71,21 +71,33 @@ CAP Java 5.0 increased some minimum required versions: | XSUAA (BTP Security Library) | 4.0.0 | | Maven | 3.9.10 | - +| `cds.errors.combined` | Was deprecated since CAP Java 4.0. The property had no effect anymore and has been removed. | +| `cds.mcp.autoConfig` | Use `cds.mcp.autoWired`. | +| `cds.taskScheduler.enabled` | Use `cds.outbox.persistent.scheduler.enabled`. | +| `cds.sql.hana. optimizationMode ` | Was deprecated since CAP Java 4.0. SAP HANA's HEX engine is used ever since. | ### Removed Java APIs { #removed-java-apis-4-to-5 } @@ -112,7 +127,7 @@ Removed deprecated methods: | `c.s.c.services.ServiceExceptionUtils.getMessageTarget(String target)` | `MessageTarget.create(target)` | | `c.s.c.services.ServiceExceptionUtils.getMessageTarget(String parameter, Class type, Function path)` | `MessageTarget.create(parameter, type, path)` | | `c.s.c.services.ServiceExceptionUtils.getMessageTarget(String parameter, Function path)` | `MessageTarget.create(parameter, path)` | - +| `c.s.c.reflect.CdsEntity.isAbstract() ` | always `false` | ### Changes in the `cds-maven-plugin` There are some incompatibilities in the [`cds-maven-plugin`](./assets/cds-maven-plugin-site/plugin-info.html) between version 4.9.x and 5.0.0, which require adjustments in the pom.xml of a CAP Java application when upgrading to CAP Java 5.0.0. @@ -156,7 +171,6 @@ The internally used maven modules `repackaged/odata-v4-lib` and `repackaged/odat 3. Use upstream open-source Apache Olingo. Change dependencies from corresponding internal CAP `mvn` modules to OSS packages `org.apache.olingo:olingo-odata4`, `org.apache.olingo:olingo-odata2` - ## CAP Java 3.10 to CAP Java 4.0 { #three-to-four } ### New License