-
Notifications
You must be signed in to change notification settings - Fork 41k
Spring Boot 3.5.0 RC1 Release Notes
Thus far, Spring Boot auto-configures a TaskExecutor
with the taskExecutor
and applicationTaskExecutor
bean names.
As of this release, only the applicationTaskExecutor
bean name is provided.
Code that is requesting the auto-configured Executor
by name should be adapted to use applicationTaskExecutor
.
If you relied on this behaviour and cannot change it immediately, the alias can be added using a BeanFactoryPostProcessor
, as shown in the following example:
@Configuration
public class MyConfiguration {
@Bean
static BeanFactoryPostProcessor taskExecutorAliasBeanFactoryPostProcessor() {
return (beanFactory) -> beanFactory.registerAlias("applicationTaskExecutor", "taskExecutor");
}
}
Tip
|
Check the configuration changelog for a complete overview of the changes in configuration. |
If an Executor
bean is present, Spring Boot can now be configured to auto-configure an AsyncTaskExecutor
anyway.
To do so, set the spring.task.execution.mode
property to force
.
When running in this mode, it makes sure that all integrations, including regular @Async
processing uses the auto-configured executor,
unless an AsyncConfigurer
bean is defined.
Spring Boot 3.5.0-RC1 moves to new versions of several Spring projects:
TBD
Numerous third-party dependencies have also been updated, some of the more noteworthy of which are the following:
TBD
Apart from the changes listed above, there have also been lots of minor tweaks and improvements including:
-
MeterProvider
beans are now automatically configured onOtlpHttpLogRecordExporter
,OtlpHttpSpanExporter
,OtlpGrpcLogRecordExporter
andOtlpGrpcSpanExporter
. -
The
referral
mode for Spring LDAP can be configured with the newspring.ldap.referral
property. -
Customizers for
OtlpHttpSpanExporterBuilder
andOtlpGrpcSpanExporterBuilder
have been added. -
The new property
spring.kafka.consumer.max-poll-interval
can be used to configure Kafka’s maximum delay between poll invocations.