In Spring Boot 3.2.x, the underlying code that supports Spring Boot’s "Uber Jar" loading has been rewritten now that we no longer need to support Java 8. The updated code makes use of a new URL format which is more compliant with JDK expectations (more details.
This change broke the SCDF metadata loading code as we use the Boot loader to dig around jars for metadata.
The workaround was to use the CLASSIC loader.
We should investigate how to get onto the default loader as eventually the CLASSIC loader will be deprecated and removed.
I did play around w/ it for a bit but did not have success.
In Spring Boot 3.2.x, the underlying code that supports Spring Boot’s "Uber Jar" loading has been rewritten now that we no longer need to support Java 8. The updated code makes use of a new URL format which is more compliant with JDK expectations (more details.
This change broke the SCDF metadata loading code as we use the Boot loader to dig around jars for metadata. The workaround was to use the
CLASSICloader.We should investigate how to get onto the default loader as eventually the
CLASSICloader will be deprecated and removed.I did play around w/ it for a bit but did not have success.