. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 8.19. Data Model changes for Apache Unomi 1.5.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 8.19.2. API changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 8.20. Important changes in public servlets and install Java SE 8 or greater. JDK COMPATIBILITY Starting with Java 9, Oracle made some big changes to the Java platform releases. This is why Apache Unomi is focused on supporting the Long Term Supported

robustness of the product. The introduction of tighter data validation with JSON Schemas required some changes in the product data model, which presented an opportunity for noticeable improvements in the overall using the default Apache 1.x data model, our Unomi 2 migration process will handle the data model changes for you. If you are using custom events/objects, please refer to the detailed migration guide for and install Java SE 11 or greater. JDK COMPATIBILITY Starting with Java 9, Oracle made some big changes to the Java platform releases. This is why Apache Unomi is focused on supporting the Long Term Supported