The CustomUriTagProvider class has been renamed to CustomKeyValueProvider. This is due to the fact that Spring 3.2 dropped some classes and the code now uses their replacement. This replacement class no longer uses the Tag class, but the KeyValue and KeyValues classes.
Methods in the rest controller classes now explicitly include parameter names in the @PathVariable and @RequestParameter annotations, otherwise the parameters are not recognized.
Description
This PR addresses #380.
The
CustomUriTagProviderclass has been renamed toCustomKeyValueProvider. This is due to the fact that Spring 3.2 dropped some classes and the code now uses their replacement. This replacement class no longer uses theTagclass, but theKeyValueandKeyValuesclasses.Starting with Spring Framework 6.1 (Spring Boot 3.3 brings version 6.1.8), Spring's
LocalVariableTableParameterNameDiscoverercan no longer be used to discover parameter names, see https://github.com/spring-projects/spring-framework/wiki/Upgrading-to-Spring-Framework-6.x#parameter-name-retention. This required some changes in the code:Methods in the rest controller classes now explicitly include parameter names in the
@PathVariableand@RequestParameterannotations, otherwise the parameters are not recognized.When using the
@Cacheableannotation (e.g. inSemanticsHubFacade), it is no longer possible to use a SpEl expression like"#urn"to specify the caching key. Instead, the code now needs a SpEl-Expression like"#p0", see https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/cache/annotation/Cacheable.html#key().Pre-review checks
Please ensure to do as many of the following checks as possible, before asking for committer review: