That pull request only addresses the db connection and querying issues. It's a bit similar to @sbrunner's #3943, but doesn't touch the CI/CD test running workflows

Thanks for the fixes. Could you please add a test, justifying why these changes were required ?

The failure happens because of the difference in the mapfish_spring_hibernate.xml files:

• test/.../mapfish_spring_hibernate.xml had the line "org.mapfish.print.servlet.job"
• src/.../mapfish_spring_hibernate.xml didn't have this line

So the tests were not validating the behavior at runtime.

The last commit (ef04b27) is needed to reduce amount of the database structure changes, e.g.:

The full DB structure comparison was done using the following steps:

1. Start DB and the print server based on the "old" spring.
2. Do 100 print requests, then dump the database contents (spring5_dump.sql.zip)
3. Stop the spring5 print server, start the spring 7 print serve, dump the database contents (spring7_dump.sql.zip)
4. Do 100 print requests, then dump the database contents (spring7_updated_dump.sql.zip)

The results were in line with expectations:

• spring5_dump.sql and spring7_dump.sql have exactly the same CREATE and COPY statements, which means the migration will not destroy an existing data.
• spring5_dump.sql and spring7_dump_updated.sql have exactly the same CREATE statements, the COPY statement has 200 lines (100 from step 2, 100 more from step 4).

Current status: one failing test, "PrintApiTest > testSecuredTemplate_CreateMap()"

Test fails when running acceptance tests in clustering mode. Not a regression, because it failed with the same error before spring7 migration and after the migration.

Current status: one failing test, "PrintApiTest > testSecuredTemplate_CreateMap()"

Test fails when running acceptance tests in clustering mode. Not a regression, because it failed with the same error before spring7 migration and after the migration.

=> 6c82a26