Fix failing tests after Spring Boot upgrade to 3.2.2

Upgraded Spring-Boot version to 3.2.2 without upgrading Hibernate, so now we have dependency to Hibernate version 6.3.1 Final. Once Hibernate resolves the issue with JsonType, and we will track for now the issue mentioned by me in my previous comment, then we will upgrade it’s version.

The investigation has revealed that this issue is most likely related to and comes from the Hibernate framework. What was working with version 6.3.1 final of the framework started to work differently after the upgrade to the version 6.4.1 final (through upgrading to Spring Boot 3.2.2) and out integration tests have detected it. The nature of the issue is as follows: when new authority records are created in DB (insert query) Hibernate updates these records (update query) once the records are created. This is happening as part of the flush operation for the insert. Hibernate performs update because of the dirty checking step which is for some reason detects that four attributes of authority record (identifiers, notes, saftHeadings, sftHeadings and they are stored as json in the DB) are modified.

This issue would not affect authority management logic in terms of the business perspective except for the optimistic locking as version attribute is being incremented twice in above described case.

Similar issue was already reported in hibernate’s issue tracker