You are viewing the documentation for Blueriq 15. Documentation for other versions is available in our documentation directory.
Before you upgrade make sure to read the General Upgrade instructions as well as the Upgrade instructions for previous versions.
The changes are color coded. Orange elements have been changed, Green elements have been added and Red elements have been removed compared to the 15.x release.
Table of contents
Enhancing container identification
With this release we have enhanced container identification, by doing so we have seen in our own regression tests that events of the search field for AQ_Instance_List are different: the unique container ID is now included in the parameter name of the search field. Keep in mind that this might affect your own UI tests.
Spring Boot 2.7
The runtime has been upgraded to Spring Boot 2.7.1. If you don't have any custom code, there are no specific upgrade instructions. If you do, please refer to the Spring Boot 2.7 release notes to see if you are affected.
WebSecurityConfigurerAdapter deprecation
In Spring Security 5.7, which comes with Spring Boot 2.7, the WebSecurityConfigurerAdapter
class was made deprecated. We updated the runtime to use the suggested alternative (component based configuration). The runtime will not start if Spring Security detects a mix of components and WebSecurityConfigurerAdapter
classes, so if you have any classes in your custom code that extend from this class, you need to migrate these to component based configuration. This article describes how you need to update your code.
Example:
@Configuration @Order(42) public class CustomRuntimeWebSecurityConfigurer extends WebSecurityConfigurerAdapter { @Override protected void configure(HttpSecurity http) throws Exception { http.authorizeRequests().antMatchers("/server/my-url/**").denyAll(); } }
@Configuration public class CustomRuntimeWebSecurityConfigurer { @Bean @Order(42) protected SecurityFilterChain customRuntimeWebSecurityChain(HttpSecurity http) throws Exception { http.authorizeRequests().antMatchers("/server/my-url/**").denyAll(); return http.build(); } }
Note that the @Order
annotation needs to move from the configuration class to the bean definition, if it is present at all.
Embedded H2 fallback removed
The runtime no longer provides a default fallback to an in memory H2 database when neither the externaldatasources
nor the jndidatasources
Spring profiles were enabled. If you rely on this configuration, you will need to configure the H2 datasources as external datasources and enable the externaldatasources
Spring profile. Additionally, you need to set the blueriq.datasource.h2.enabled
property to true
.
Known issues
For an overview of known issue please refer to: Known issues.