I spent my time at the CodeCamp working on our License Oder Ivy App. In addition to a new REST API, I also began the migration of the projects from ivy13.2 to ivy14 and I think it's worth sharing a few experiences here.
First of all I used the ivy project conversion in the visual studio code designer, that made a pretty good job. However the world is more complex and I encountered some migration issues, that had to be solved afterwards.
jakarta.faces replacemenet of javax.faces classes
- the ivy project converter does not auto convert javax.faces classes to jakarta.faces classes in ivyscript code blocks. For example this was used to set server side validation error rmessages.
primefaces15
- layouting issues, e.g. h:panelGroup in a p:panelGrid behave different
- some primefaces elements do no longer support the same set of attributes. -> consult the primefaces migi notes for details.
- charts in primefaces15 are total different than in the older primefaces versions. The AI Copilot's support was very helpfull during the migration.
Public API
- some deprecated ivy public API have now been removed e.g wf.application.name() was used to build navigation links by code instead of calling appropriate provided methods like ivy.html.startLink()
Tests
- some tests do currently not run in visual studio code, because there is an issue in the test setup (missing test.engine.url system property)
