Skip to Content

Changes for page 224 - Summer Sonata

Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 459.1
edited by Carlijn Kokkeler
on 2024/04/10 11:55
Change comment: There is no comment for this version
To version 460.1
edited by Carlijn Kokkeler
on 2024/04/10 11:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -21,7 +21,7 @@
21 21  
22 22  {{info}}In our continued efforts to make the transition to Spring 6 as smooth as possible we have written down the advised process for identifying and updating the relevant flows as a consequence of the Spring 6 migration, which you can find [[here>>doc:Main.eMagiz Support.Migration Paths.migration-path-spring-6-migration.WebHome||target="blank"]].
23 23  
24 -This large maintenance update, moving the eMagiz runtime stack from Spring 5 to Spring 6 and from Java 8 to Java 17, includes moving to latest (major) versions of open source projects, libraries and technologies. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]] will be released. Although no new functionality is added in this new image version, several Spring libraries have been changed significantly. More information can be found [[runtime image>>doc:Main.Release Information.Runtime Images.V300.WebHome||target="blank"]]. {{/info}}
24 +This large maintenance update, moving the eMagiz runtime stack from Spring 5 to Spring 6 and from Java 8 to Java 17, includes moving to latest (major) versions of open source projects, libraries and technologies. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]] will be released. Although no new functionality is added in this new image version, several Spring libraries have been changed significantly. More information can be found [[here>>doc:Main.Release Information.Runtime Images.V300.WebHome||target="blank"]]. {{/info}}
25 25  
26 26  {{info}}Please be aware that we will create autosaved versions for affected flows still running on the legacy runtime architecture. This way, we ensure consistency in what the user sees when working with flow components in the Create phase while at the same time prepare your model for a future migration to the current runtime architecture. Should you need to make a functional change in one of these affected flows, you can do so without a deployment and without using Spring 6 in your legacy runtime. {{/info}}
27 27