Deprecated API
Contents
-
ElementDescriptionas of 6.0.12 in favor of the buildersince 6.0.10, as it is not used by the framework anymoreas of 6.0.1, in favor of
StandardReflectionParameterNameDiscoverer
(with the "-parameters" compiler flag)ConcurrentExecutorAdapter
is obsolete and will be removed in Spring Framework 6.1as of 6.0, in favor ofSocketConfig.Builder.setSoTimeout(Timeout)
, see above.in favor ofClientHttpObservationDocumentation.LowCardinalityKeyNames.CLIENT_NAME
; scheduled for removal in 6.2. This will be available both as a low and high cardinality key value.as of 6.0, in favor ofClientHttpResponse.getStatusCode()
as of 6.0, in favor ofPartEvent
andPartEventHttpMessageReader
in favor ofHttpMethod.valueOf(String)
as of Spring Framework 6.0 in favor ofHttpRequest.getMethod()
andHttpMethod.name()
as of 6.0.3, in favor ofMediaType.APPLICATION_GRAPHQL_RESPONSE
as of 6.0.3, in favor ofMediaType.APPLICATION_GRAPHQL_RESPONSE_VALUE
As of 6.0, with no direct replacementAs of 6.0, with no direct replacementAs of 6.0, in favor ofMimeTypeUtils.sortBySpecificity(List)
As of 6.0, with no direct replacementsince 6.0.8, in favor ofAbstractServerHttpRequest(HttpMethod, URI, String, MultiValueMap)
since 6.0.8, in favor ofAbstractServerHttpRequest(HttpMethod, URI, String, MultiValueMap)
as of 5.3, in favor ofCronExpression
as of 5.3, in favor ofCronExpression.parse(String)
as of 6.0, in favor ofExchangeResult.getStatus()
as of 4.3.7, in favor ofAssert.doesNotContain(String, String, String)
; to be removed in 6.1as of 4.3.7, in favor ofAssert.hasLength(String, String)
; to be removed in 6.1as of 4.3.7, in favor ofAssert.hasText(String, String)
; to be removed in 6.1as of 4.3.7, in favor ofAssert.isNull(Object, String)
; to be removed in 6.1as of 4.3.7, in favor ofAssert.isTrue(boolean, String)
; to be removed in 6.1as of 4.3.7, in favor ofAssert.noNullElements(Object[], String)
; to be removed in 6.1as of 4.3.7, in favor ofAssert.notEmpty(Object[], String)
; to be removed in 6.1as of 4.3.7, in favor ofAssert.notEmpty(Collection, String)
; to be removed in 6.1as of 4.3.7, in favor ofAssert.notEmpty(Map, String)
; to be removed in 6.1as of 4.3.7, in favor ofAssert.notNull(Object, String)
; to be removed in 6.1as of 4.3.7, in favor ofAssert.state(boolean, String)
; to be removed in 6.1as of Spring Framework 6.0.5 in favor ofBase64
; scheduled for removal in 6.2As of 6.0, with no direct replacementAs of 6.0, with no direct replacementin favor of usingServerWebExchangeContextFilter.getExchange(ContextView)
which accepts aContextView
instead ofContext
, reflecting the fact that theContextView
is needed only for reading.in favor ofClientHttpObservationDocumentation.LowCardinalityKeyNames.CLIENT_NAME
; scheduled for removal in 6.2. This will be available both as a low and high cardinality key value.as of 6.0, in favor ofClientResponse.statusCode()
without a replacement; for internal invocation only, not used as of 6.0in favor of checking viaHandlerResult.getExceptionHandler()
as of 6.0.3, in favor ofStandardWebSocketClient
as of 6.0 sinceModelAttributeMethodProcessor
now raises theMethodArgumentNotValidException
subclass instead.as of 6.0 sinceModelAttributeMethodProcessor
now raises theMethodArgumentNotValidException
subclass instead.as of 6.0.3, in favor ofStandardWebSocketClient
-
InterfaceDescriptionas of 6.0, in favor of
AsyncTaskExecutor.submitCompletable(Runnable)
andAsyncTaskExecutor.submitCompletable(Callable)
as of 6.0 in favor of using CSS, without direct replacementas of 6.0 in favor of using CSS, without direct replacementas of 6.0 in favor of using CSS, without direct replacementas of 6.0, in favor ofCompletableFuture.whenComplete(BiConsumer)
as of 6.0, in favor ofCompletableFuture
as of 6.0, in favor ofCompletableFuture.whenComplete(BiConsumer)
as of 6.0, in favor ofCompletableFuture.whenComplete(BiConsumer)
as of 5.3.9 in favor of using thecheckNotModified
methods inWebRequest
, or from an annotated controller method, returning aResponseEntity
with an "ETag" and/or "Last-Modified" headers set.as of 6.0 in favor of using CSS, without direct replacement
-
ClassDescriptionin
spring-jcl
(effectively equivalent toNoOpLog
)since it is only meant to be used in the above-mentioned fallback scenarioThis class should only be used by the runtime-hints agent when instrumenting bytecode and is not considered public API.as of 5.2, along withPropertyPlaceholderConfigurer
as of 5.2; useorg.springframework.context.support.PropertySourcesPlaceholderConfigurer
instead which is more flexible through taking advantage of theEnvironment
andPropertySource
mechanisms.as of 5.3, in favor of Spring's common bean definition formats and/or custom reader implementationsas of 6.0 in favor of implementingCachingConfigurer
directlyas of 6.0 in favor of implementingJCacheConfigurer
directlysince 6.0.10, as it is not used by the framework anymoreas of 6.0.1, in favor ofStandardReflectionParameterNameDiscoverer
(with the "-parameters" compiler flag)ConcurrentExecutorAdapter
is obsolete and will be removed in Spring Framework 6.1as of 6.0, with no direct replacement; scheduled for removal in 6.2as of 5.3, in favor of Spring's common bean definition formats and/or custom reader implementationsas of 6.0, in favor ofCompletableFutureReturnValueHandler
since 6.0, useio.r2dbc.spi.Parameter
instead.as of 6.0 in favor of implementingAsyncConfigurer
directlyas of 6.0, in favor ofCompletableFuture
as of 5.3, in favor ofCronExpression
as of 6.0, in favor of a straightJtaTransactionManager
definitionas of 5.3, in favor of the default methods on theTransactionSynchronization
interfaceas of 6.0 in favor of using CSS, without direct replacementas of 6.0 in favor of using CSS, without direct replacementas of 6.0 in favor of using CSS, without direct replacementas of 6.0 in favor of using CSS, without direct replacementas of Spring Framework 6.0.5 in favor ofBase64
; scheduled for removal in 6.2as of 6.0, with no concrete replacementas of 6.0, with no concrete replacementas of 6.0, in favor ofCompletableFuture
as of 6.0, with no concrete replacementas of 6.0, with no concrete replacementas of 6.0, in favor ofMono.toFuture()
as of 6.0, in favor ofCompletableFuture
As of 6.0, with no direct replacementas of 5.2.4. See class-level note inContentNegotiationManagerFactoryBean
on the deprecation of path extension config options.as of 5.2.4. See class-level note inContentNegotiationManagerFactoryBean
on the deprecation of path extension config options.as of Spring 5.1 in favor of usingHttpHeaders.setBasicAuth(String, String)
while building the request.as of 6.0.3, in favor ofStandardWebSocketClient
as of 6.0, with no direct replacementas of 6.0 in favor of using CSS, without direct replacementas of 6.0 in favor of using CSS, without direct replacementas of 6.0 in favor of using CSS, without direct replacementas of 6.0 in favor of using CSS, without direct replacementas of 6.0 in favor of using CSS, without direct replacementas of 5.3, in favor of Spring's common view resolver variants and/or custom resolver implementationsas of 5.3, in favor of Spring's common view resolver variants and/or custom resolver implementationsas of 6.0.3, in favor ofStandardWebSocketClient
as of 6.0 in favor ofResponseCookie
-
ExceptionsDescriptionas of 5.3.16 since the common executors do not support start timeoutsas of 6.0.3, in favor of
PessimisticLockingFailureException
/CannotAcquireLockException
as of 6.0.3 since it is not in use within core JDBC/ORM supportas of 6.0.3, in favor ofPessimisticLockingFailureException
/CannotAcquireLockException
as of 6.0, in favor of standardServletException
nesting
-
FieldDescriptionUse
ClassReader.readByte(int)
and the other read methods instead. This field will eventually be deleted.as of Spring 3.0: If you are using mixed autowiring strategies, prefer annotation-based autowiring for clearer demarcation of autowiring needs.as of Spring 3.0: If you are using mixed autowiring strategies, use annotation-based autowiring for clearer demarcation of autowiring needs.this customizer might result in unexpected class leak since key object still holds a strong reference to the Object and class. It is recommended to have pre-processing method that would strip Objects and represent Classes as Stringsas of 5.2.6 since theMergedAnnotations
model always ignores lang annotations according to theAnnotationFilter.PLAIN
filter (for efficiency reasons)as of 5.3.16 along withAsyncTaskExecutor.execute(Runnable, long)
as of 5.3.16 along withAsyncTaskExecutor.execute(Runnable, long)
as of 6.0.3, in favor ofMediaType.APPLICATION_GRAPHQL_RESPONSE
as of 6.0.3, in favor ofMediaType.APPLICATION_GRAPHQL_RESPONSE_VALUE
as of 5.2 in favor ofMediaType.APPLICATION_JSON
since major browsers like Chrome now comply with the specification and interpret correctly UTF-8 special characters without requiring acharset=UTF-8
parameter.as of 5.2 in favor ofMediaType.APPLICATION_JSON_VALUE
since major browsers like Chrome now comply with the specification and interpret correctly UTF-8 special characters without requiring acharset=UTF-8
parameter.as of 5.2 in favor ofMediaType.APPLICATION_PROBLEM_JSON
since major browsers like Chrome now comply with the specification and interpret correctly UTF-8 special characters without requiring acharset=UTF-8
parameter.as of 5.2 in favor ofMediaType.APPLICATION_PROBLEM_JSON_VALUE
since major browsers like Chrome now comply with the specification and interpret correctly UTF-8 special characters without requiring acharset=UTF-8
parameter.as of 5.3, see notice onMediaType.APPLICATION_STREAM_JSON_VALUE
.as of 5.3 since it originates from the W3C Activity Streams specification which has a more specific purpose and has been since replaced with a different mime type. UseMediaType.APPLICATION_NDJSON
as a replacement or any other line-delimited JSON format (e.g. JSON Lines, JSON Text Sequences).As of 6.0, with no direct replacementAs of 6.0, with no direct replacementAs of 6.0, with no direct replacementas of 6.0, with no direct replacementas of 6.0, with no direct replacementas of 6.0, with no direct replacementas of 5.3 in favor ofUrlPathHelper.PATH_ATTRIBUTE
andServletRequestPathUtils.PATH_ATTRIBUTE
. To access the cached path used for request mapping, useServletRequestPathUtils.getCachedPathValue(ServletRequest)
.as of 6.0, with no direct replacement
-
MethodDescriptionin favor of
LogFactory.getLog(Class)
/LogFactory.getLog(String)
in favor ofLogFactory.getLog(Class)
in favor ofLogFactory.getLog(String)
this method is superseded byClassWriter.newHandle(int, String, String, String, boolean)
.as of Spring 5.0, following the deprecation ofClass.newInstance()
in JDK 9Only to keep backward compatibility.as of 5.2.2, in favor ofAbstractResourceBasedMessageSource.getDefaultLocale()
as of 5.2 since it is superseded by theMergedAnnotations
APIas of 5.2 since it is superseded by theMergedAnnotations
APIas of 5.2 since it is superseded by theMergedAnnotations
APIas of 5.2 since it is superseded by theMergedAnnotations
APIas of 5.2 since it is superseded by theMergedAnnotations
APIas of 5.2 since it is superseded by theMergedAnnotations
APIas of 5.2 since it is superseded by theMergedAnnotations
APIas of 5.2 since it is superseded by theMergedAnnotations
APIas of 5.2 since it is superseded by theMergedAnnotations
APIas of 5.2 since it is superseded by theMergedAnnotations
APIas of 5.2, please implementDecoder.decode(DataBuffer, ResolvableType, MimeType, Map)
insteadas of 5.1 in favor ofEnvironment.acceptsProfiles(Profiles)
orEnvironment.matchesProfiles(String...)
since 5.2 in favor ofmethodParameter.withContainingClass(implementationClass).getParameterType()
as of 6.0, in favor ofDataBuffer.toByteBuffer(ByteBuffer)
,DataBuffer.readableByteBuffers()
, orDataBuffer.writableByteBuffers()
.as of 6.0, in favor ofDataBuffer.toByteBuffer(int, ByteBuffer, int, int)
,DataBuffer.readableByteBuffers()
, orDataBuffer.writableByteBuffers()
.as of 6.0, in favor ofDataBuffer.ensureWritable(int)
, which has different semanticssince 6.0, in favor ofDataBuffer.ensureWritable(int)
as of 6.0, in favor ofDataBuffer.split(int)
, which has different semanticsas of 6.0, in favor ofDataBuffer.split(int)
, which has different semanticsas of 6.0.5, in favor ofDataBuffer.toByteBuffer(ByteBuffer)
as of 6.0.5, in favor ofDataBuffer.toByteBuffer(int, ByteBuffer, int, int)
as of 6.0, in favor ofDataBufferFactory.allocateBuffer(int)
as of 6.0 in favor ofSpringFactoriesLoader.load(Class, ArgumentResolver, FailureHandler)
since 5.2 in favor of retaining the original MethodParameter and usingMethodParameter.nested(Integer)
if nesting is requiredas of 5.0, in favor ofMethodParameter.forExecutable(java.lang.reflect.Executable, int)
since 5.2 in favor ofMethodParameter.nested(Integer)
since 5.2 in favor ofMethodParameter.withTypeIndex(int)
as of 6.0, in favor of custom exception messages with selective inclusion of cause messagesin favor ofAsyncTaskExecutor.submitCompletable(Runnable)
in favor ofAsyncTaskExecutor.submitCompletable(Callable)
as of 5.3.16 since the common executors do not support start timeoutsuseassertThat(sourceFile)
rather than calling this method directly.useassertThat(sourceFile)
rather than calling this method directly.as of 6.0, in favor ofClientHttpResponse.getStatusCode()
; scheduled for removal in 6.2as of 6.0, in favor ofSocketConfig.Builder.setSoTimeout(Timeout)
, see above.as of 6.0, in favor ofClientHttpResponse.getStatusCode()
as of 5.1.13, useCodecConfigurer.CustomCodecs.register(Object)
orCodecConfigurer.CustomCodecs.registerWithDefaultConfig(Object)
instead.as of 5.1.13, useCodecConfigurer.CustomCodecs.register(Object)
orCodecConfigurer.CustomCodecs.registerWithDefaultConfig(Object)
instead.as of 5.1.13, useCodecConfigurer.CustomCodecs.register(Object)
orCodecConfigurer.CustomCodecs.registerWithDefaultConfig(Object)
instead.as of 5.1.13, useCodecConfigurer.CustomCodecs.register(Object)
orCodecConfigurer.CustomCodecs.registerWithDefaultConfig(Object)
instead.as of 6.0, in favor ofPartEvent
andPartEventHttpMessageReader
since 5.2.3 as per RFC 6266, Appendix B, to be removed in a future release.since 5.2.3 as per RFC 6266, Appendix B, to be removed in a future release.since 5.2.3 as per RFC 6266, Appendix B, to be removed in a future release.since 5.2.3 as per RFC 6266, Appendix B, to be removed in a future release.since 5.2.3 as per RFC 6266, Appendix B, to be removed in a future release.since 5.2.3 as per RFC 6266, Appendix B, to be removed in a future release.since 5.2.3 as per RFC 6266, Appendix B, to be removed in a future release.since 5.2.3 as per RFC 6266, Appendix B, to be removed in a future release.in favor ofHttpMethod.valueOf(String)
as of Spring Framework 6.0 in favor ofHttpRequest.getMethod()
andHttpMethod.name()
as of 5.3, in favor of invokingHttpStatus.series()
directlyAs of 6.0, with no direct replacementAs of 6.0, in favor ofMimeTypeUtils.sortBySpecificity(List)
As of 6.0, in favor ofMimeTypeUtils.sortBySpecificity(List)
as of 6.0, in favor ofResponseEntity.getStatusCode()
; scheduled for removal in 7.0originally introduced for Undertow to stop write notifications when no data is available, but deprecated as of 5.0.6 since constant switching on every requested item causes a significant slowdown.as of 6.0, in favor ofServerHttpResponse.getStatusCode()
as of 5.3, in favor ofJdbcOperations.query(String, ResultSetExtractor, Object...)
as of 5.3, in favor ofJdbcOperations.query(String, RowCallbackHandler, Object...)
as of 5.3, in favor ofJdbcOperations.query(String, RowMapper, Object...)
as of 5.3, in favor ofJdbcOperations.queryForList(String, Class, Object...)
as of 5.3, in favor ofJdbcOperations.queryForObject(String, Class, Object...)
as of 5.3, in favor ofJdbcOperations.queryForObject(String, RowMapper, Object...)
as of 5.1.11, in favor ofDataSourceUtils.resetConnectionAfterTransaction(Connection, Integer, boolean)
as of Spring Framework 5.2.16 with no plans for replacement. This is an internal API and will likely be removed in Spring Framework 6.0.as of Spring Framework 5.2.16 with no plans for replacement. This is an internal API and will likely be removed in Spring Framework 6.0.as of Spring Framework 5.2.16 with no plans for replacement. This is an internal API and will likely be removed in Spring Framework 6.0.as of Spring Framework 5.2.16 with no plans for replacement. This is an internal API and will likely be removed in Spring Framework 6.0.as of Spring Framework 5.2.16 with no plans for replacement. This is an internal API and will likely be removed in Spring Framework 6.0.as of Spring Framework 5.2.16 with no plans for replacement. This is an internal API and will likely be removed in Spring Framework 6.0.as of Spring Framework 5.2.16 with no plans for replacement. This is an internal API and will likely be removed in Spring Framework 6.0.as of 5.3.29, in favor ofSQLWarningException.getSQLWarning()
as of 5.3, in favor of the JDBC 4.0 connection validationas of 5.2.9, in favor ofJdbcUtils.extractDatabaseMetaData(DataSource, DatabaseMetaDataCallback)
with a lambda expression or method reference and a generically typed resultas of 6.0, in favor ofAsyncHandlerMethodReturnValueHandler.toCompletableFuture(Object, MethodParameter)
as of 5.3 in favor ofRSocketRequester.Builder.transport(ClientTransport)
as of 5.3 in favor ofRSocketRequester.Builder.tcp(String, int)
as of 5.3 in favor ofRSocketRequester.Builder.websocket(URI)
as of 6.0, in favor ofConnectionHandlingStompSession.getSession()
as of 6.0, in favor ofReactorNettyTcpStompClient.connectAsync(StompHeaders, StompSessionHandler)
as of 6.0, in favor ofReactorNettyTcpStompClient.connectAsync(StompSessionHandler)
as of 6.0, in favor ofTcpConnection.sendAsync(Message)
as of 6.0, in favor ofTcpOperations.connectAsync(TcpConnectionHandler)
as of 6.0, in favor ofTcpOperations.connectAsync(TcpConnectionHandler, ReconnectStrategy)
as of 6.0, in favor ofTcpOperations.shutdownAsync()
as of Spring Framework 6.0 in favor ofMockServerHttpRequest.method(HttpMethod, String, Object...)
as of 5.0.4, in favor of a customHibernateCallback
lambda code block passed to the generalHibernateOperations.execute(org.springframework.orm.hibernate5.HibernateCallback<T>)
methodas of 5.0.4, in favor of a customHibernateCallback
lambda code block passed to the generalHibernateOperations.execute(org.springframework.orm.hibernate5.HibernateCallback<T>)
methodas of 5.0.4, in favor of a customHibernateCallback
lambda code block passed to the generalHibernateOperations.execute(org.springframework.orm.hibernate5.HibernateCallback<T>)
methodas of 5.0.4, in favor of a customHibernateCallback
lambda code block passed to the generalHibernateOperations.execute(org.springframework.orm.hibernate5.HibernateCallback<T>)
methodas of 5.0.4, in favor of a customHibernateCallback
lambda code block passed to the generalHibernateOperations.execute(org.springframework.orm.hibernate5.HibernateCallback<T>)
methodas of 5.0.4, in favor of a customHibernateCallback
lambda code block passed to the generalHibernateOperations.execute(org.springframework.orm.hibernate5.HibernateCallback<T>)
methodas of 5.0.4, in favor of a customHibernateCallback
lambda code block passed to the generalHibernateOperations.execute(org.springframework.orm.hibernate5.HibernateCallback<T>)
methodas of 5.0.4, in favor of a customHibernateCallback
lambda code block passed to the generalHibernateOperations.execute(org.springframework.orm.hibernate5.HibernateCallback<T>)
methodas of 5.0.4, in favor of a customHibernateCallback
lambda code block passed to the generalHibernateOperations.execute(org.springframework.orm.hibernate5.HibernateCallback<T>)
methodas of 5.0.4, in favor of a customHibernateCallback
lambda code block passed to the generalHibernateOperations.execute(org.springframework.orm.hibernate5.HibernateCallback<T>)
methodas of 5.0.4, in favor of a customHibernateCallback
lambda code block passed to the generalHibernateOperations.execute(org.springframework.orm.hibernate5.HibernateCallback<T>)
methodas of 5.3.29 since Hibernate 5.x aggressively closes ResultSets on commit, making it impossible to rely on ResultSet holdability. Also, Spring does not provide an equivalent setting onJpaTransactionManager
.as of 5.3.9, in favor of directThreadPoolTaskScheduler.getScheduledThreadPoolExecutor()
accessas of 6.0, in favor ofIntervalTask.getInitialDelayDuration()
as of 6.0, in favor ofIntervalTask.getIntervalDuration()
as of 6.0, in favor ofScheduledTaskRegistrar.addFixedDelayTask(Runnable, Duration)
as of 6.0, in favor ofScheduledTaskRegistrar.addFixedRateTask(Runnable, Duration)
as of 6.0, in favor onPeriodicTrigger.getInitialDelayDuration()
as of 6.0, in favor onPeriodicTrigger.getPeriodDuration()
as of 6.0, with no direct replacementas of 6.0, in favor ofPeriodicTrigger.setInitialDelay(Duration)
as of 6.0, in favor ofSimpleTriggerContext.update(Instant, Instant, Instant)
as of 6.0, in favor ofTaskScheduler.schedule(Runnable, Instant)
as of 6.0, in favor ofTaskScheduler.scheduleAtFixedRate(Runnable, Duration)
as of 6.0, in favor ofTaskScheduler.scheduleAtFixedRate(Runnable, Instant, Duration)
as of 6.0, in favor ofTaskScheduler.scheduleWithFixedDelay(Runnable, Duration)
as of 6.0, in favor ofTaskScheduler.scheduleWithFixedDelay(Runnable, Instant, Duration)
as of 6.0, in favor ofTrigger.nextExecution(TriggerContext)
as of 6.0, in favor onTriggerContext.lastActualExecution()
as of 6.0, in favor onTriggerContext.lastCompletion()
as of 6.0, in favor onTriggerContext.lastScheduledExecution()
as of Spring Framework 6.0, in favor of methods defined in theSmartContextLoader
SPIas of Spring Framework 6.0, in favor of methods defined in theSmartContextLoader
SPIas of Spring Framework 6.0, in favor ofAbstractGenericContextLoader.loadContext(MergedContextConfiguration)
as of 6.0, in favor ofExchangeResult.getStatus()
as of 5.1.13 in favor ofWebTestClient.Builder.codecs(Consumer)
as of Spring Framework 5.2 in favor ofWebTestClient.RequestBodySpec.bodyValue(Object)
as of 6.0, seePathPatternParser.setMatchOptionalTrailingSeparator(boolean)
in favor ofStatusResultMatchers.isEarlyHints()
matching the deprecation ofHttpStatus.DESTINATION_LOCKED
matching the deprecation ofHttpStatus.INSUFFICIENT_SPACE_ON_RESOURCE
matching the deprecation ofHttpStatus.METHOD_FAILURE
in favor ofStatusResultMatchers.isFound()
matching the deprecation ofHttpStatus.REQUEST_ENTITY_TOO_LARGE
matching the deprecation ofHttpStatus.REQUEST_URI_TOO_LONG
matching the deprecation ofHttpStatus.USE_PROXY
as of Spring Framework 5.3.10, in favor ofResultActions.andExpectAll(ResultMatcher...)
as of 5.2.4. See class-level note inRequestMappingHandlerMapping
on the deprecation of path extension config options.as of 6.0, seePathPatternParser.setMatchOptionalTrailingSeparator(boolean)
as of 4.3.7, in favor ofAssert.doesNotContain(String, String, String)
; to be removed in 6.1as of 4.3.7, in favor ofAssert.hasLength(String, String)
; to be removed in 6.1as of 4.3.7, in favor ofAssert.hasText(String, String)
; to be removed in 6.1as of 4.3.7, in favor ofAssert.isNull(Object, String)
; to be removed in 6.1as of 4.3.7, in favor ofAssert.isTrue(boolean, String)
; to be removed in 6.1as of 4.3.7, in favor ofAssert.noNullElements(Object[], String)
; to be removed in 6.1as of 4.3.7, in favor ofAssert.notEmpty(Object[], String)
; to be removed in 6.1as of 4.3.7, in favor ofAssert.notEmpty(Collection, String)
; to be removed in 6.1as of 4.3.7, in favor ofAssert.notEmpty(Map, String)
; to be removed in 6.1as of 4.3.7, in favor ofAssert.notNull(Object, String)
; to be removed in 6.1as of 4.3.7, in favor ofAssert.state(boolean, String)
; to be removed in 6.1as of 5.2, in favor of custom (possibly narrower) checks such as for a Spring AOP proxyas of 5.2, in favor of custom (possibly narrower) checks or simply a check for containingClassUtils.CGLIB_CLASS_SEPARATOR
as of 5.2, in favor of custom (possibly narrower) checks or simply a check for containingClassUtils.CGLIB_CLASS_SEPARATOR
as of 6.0, in favor ofCompletableFuture.whenComplete(BiConsumer)
as of 6.0, in favor ofCompletableFuture.whenComplete(BiConsumer)
in favor ofConcurrentLruCache.capacity()
as of 6.0.This utility uses Java Object Serialization, which allows arbitrary code to be run and is known for being the source of many Remote Code Execution (RCE) vulnerabilities.Prefer the use of an external tool (that serializes to JSON, XML, or any other format) which is regularly checked and updated for not allowing RCE.
as of 6.0 in favor ofInputStream.nullInputStream()
as of 5.3, in favor ofStringUtils.hasLength(String)
andStringUtils.hasText(String)
(orObjectUtils.isEmpty(Object)
)since 6.0, in favor ofString.stripLeading()
since 6.0, in favor ofString.stripTrailing()
since 6.0, in favor ofString.strip()
as of 5.2.4. See class-level note on the deprecation of path extension config options. As there is no replacement for this method, in 5.2.x it is necessary to set it tofalse
. In 5.3 the default changes tofalse
and use of this property becomes unnecessary.as of 5.2.4. See class-level note on the deprecation of path extension config options.as of 5.0, in favor ofContentNegotiationManagerFactoryBean.setUseRegisteredExtensionsOnly(boolean)
, which has reverse behavior.as of 5.0, in favor ofAbstractMappingContentNegotiationStrategy.setUseRegisteredExtensionsOnly(boolean)
.as of 6.0, in favor ofRestClientResponseException.getStatusCode()
as of 6.0, in favor ofUnknownContentTypeException.getStatusCode()
as of 5.2, same-origin checks are performed directly byCorsUtils.isCorsRequest(org.springframework.http.server.reactive.ServerHttpRequest)
as of 5.3 in favor of usingUrlBasedCorsConfigurationSource.setUrlPathHelper(UrlPathHelper)
, if at all. For further details, please seeUrlBasedCorsConfigurationSource.setAllowInitLookupPath(boolean)
.as of 5.3 in favor ofUrlPathHelper.PATH_ATTRIBUTE
.as of 5.3 in favor of usingUrlBasedCorsConfigurationSource.setUrlPathHelper(UrlPathHelper)
, if at all. For further details, please seeUrlBasedCorsConfigurationSource.setAllowInitLookupPath(boolean)
.as of 5.3 in favor of usingUrlBasedCorsConfigurationSource.setUrlPathHelper(UrlPathHelper)
, if at all. For further details, please seeUrlBasedCorsConfigurationSource.setAllowInitLookupPath(boolean)
.in favor of usingServerWebExchangeContextFilter.getExchange(ContextView)
which accepts aContextView
instead ofContext
, reflecting the fact that theContextView
is needed only for reading.as of 6.0 without a replacement; once removed, the default model will always be ignored on redirectas of 6.0, seePathPatternParser.setMatchOptionalTrailingSeparator(boolean)
As of Spring Framework 5.2, in favor ofBodyInserters.fromValue(Object)
in favor ofClientRequest.create(HttpMethod, URI)
as of 5.3 in favor of the instance basedClientResponse.mutate()
.as of 6.0, in favor ofClientResponse.statusCode()
as of Spring 5.1 in favor of usingHttpHeaders.setBasicAuth(String, String)
while building the request.as of 5.1.13 in favor ofWebClient.Builder.codecs(Consumer)
as of Spring Framework 5.2 in favor ofWebClient.RequestBodySpec.bodyValue(Object)
in 5.3.2 to be removed soon after; this method cannot provide context to downstream (nested or subsequent) requests and is of limited value.since 5.3 due to the possibility to leak memory and/or connections; please, useWebClient.RequestHeadersSpec.exchangeToMono(Function)
,WebClient.RequestHeadersSpec.exchangeToFlux(Function)
; consider also usingWebClient.RequestHeadersSpec.retrieve()
which provides access to the response status and headers viaResponseEntity
along with error status handling.as of 6.0, in favor ofWebClientResponseException.getStatusCode()
as of 6.0, in favor ofServerRequest.method()
as of 5.3, in favor onServerRequest.requestPath()
as of Spring Framework 5.2 in favor ofServerResponse.BodyBuilder.bodyValue(Object)
as of 6.0, in favor ofServerResponse.statusCode()
as of 6.0, seePathPatternParser.setMatchOptionalTrailingSeparator(boolean)
without a replacement; for internal invocation only, not used as of 6.0in favor of checking viaHandlerResult.getExceptionHandler()
as of 5.3 in favor ofReactorNettyWebSocketClient.getWebsocketClientSpec()
as of 5.3 in favor ofReactorNettyWebSocketClient.getWebsocketClientSpec()
as of 5.3 in favor of providing a supplier ofWebsocketClientSpec.Builder
with a constructor argumentas of 5.3 in favor of providing a supplier ofWebsocketClientSpec.Builder
with a constructor argumentas of 5.3 in favor of comparing codes directlyas of 5.2.6 in favor ofReactorNettyRequestUpgradeStrategy.getWebsocketServerSpec()
as of 5.2.6 in favor ofReactorNettyRequestUpgradeStrategy.getWebsocketServerSpec()
as of 5.2.6 in favor of providing a supplier ofWebsocketServerSpec.Builder
with a constructor argumentas of 5.2.6 in favor of providing a supplier ofWebsocketServerSpec.Builder
with a constructor argumentas of 6.0, in favor ofResponseStatusExceptionHandler.determineStatus(Throwable)
as of 6.0 in favor ofMethodNotAllowedException.getHeaders()
as of 6.0 in favor ofNotAcceptableStatusException.getHeaders()
as of 6.0 in favor ofResponseStatusException.getHeaders()
as of 6.0 in favor ofUnsupportedMediaTypeStatusException.getHeaders()
as of 5.2.4. See deprecation note onContentNegotiationManagerFactoryBean.setFavorPathExtension(boolean)
.as of 5.2.4. See deprecation note onContentNegotiationManagerFactoryBean.setIgnoreUnknownPathExtensions(boolean)
.as of 5.0, in favor ofContentNegotiationConfigurer.useRegisteredExtensionsOnly(boolean)
which has reverse behavioras of 5.2.4, see deprecation note onPathMatchConfigurer.setUseRegisteredSuffixPatternMatch(Boolean)
.as of 5.2.4, see deprecation note onPathMatchConfigurer.setUseSuffixPatternMatch(Boolean)
.as of 5.2.4. See class-level note inRequestMappingHandlerMapping
on the deprecation of path extension config options.as of 5.2.4. See class-level note inRequestMappingHandlerMapping
on the deprecation of path extension config options. As there is no replacement for this method, in 5.2.x it is necessary to set it tofalse
. In 5.3 the default changes tofalse
and use of this property becomes unnecessary.as of 6.0, seePathPatternParser.setMatchOptionalTrailingSeparator(boolean)
in favor ofServerRequest.method()
as of 5.3, in favor onServerRequest.requestPath()
as of 6.0, in favor ofServerResponse.statusCode()
as of 6.0, in favor of usingAbstractHandlerMapping.setUrlPathHelper(UrlPathHelper)
as of 6.0, in favor of usingAbstractHandlerMapping.setUrlPathHelper(UrlPathHelper)
as of 6.0, in favor of usingAbstractHandlerMapping.setUrlPathHelper(UrlPathHelper)
as of 5.3 in favor of providing non-pattern mappings viaAbstractHandlerMethodMapping.getDirectPaths(Object)
insteadas of 6.0, seePathPatternParser.setMatchOptionalTrailingSeparator(boolean)
as of 5.3 in favor ofMappedInterceptor.matches(HttpServletRequest)
as of 5.3.9 along withLastModified
.org.springframework.web.servlet.i18n.CookieLocaleResolver.determineDefaultLocale(HttpServletRequest) as of 6.0, in favor ofCookieLocaleResolver.setDefaultLocaleFunction(Function)
as of 6.0, in favor ofCookieLocaleResolver.setDefaultTimeZoneFunction(Function)
as of 6.0 in favor ofCookieLocaleResolver.setCookieMaxAge(Duration)
as of 6.0 in favor ofCookieLocaleResolver(String)
as of 6.0, in favor ofSessionLocaleResolver.setDefaultLocaleFunction(Function)
as of 6.0, in favor ofSessionLocaleResolver.setDefaultTimeZoneFunction(Function)
as of 5.3.9 along withLastModified
.as of 6.0 without a replacement; once removed, the default model will always be ignored on redirectas of 5.2.4. See class-level note on the deprecation of path extension config options.as of 5.2.4. See class level note on the deprecation of path extension config options.as of 5.2.4. See class level note on the deprecation of path extension config options. As there is no replacement for this method, in 5.2.x it is necessary to set it tofalse
. In 5.3 the default changes tofalse
and use of this property becomes unnecessary.as of 6.0, seePathPatternParser.setMatchOptionalTrailingSeparator(boolean)
as of 5.2.4. See deprecation notice onRequestMappingHandlerMapping.setUseRegisteredSuffixPatternMatch(boolean)
.as of 5.2.4. See deprecation notice onRequestMappingHandlerMapping.setUseSuffixPatternMatch(boolean)
.as of 6.0 sinceModelAttributeMethodProcessor
now raises theMethodArgumentNotValidException
subclass instead.as of 5.2.4. See class-level note inRequestMappingHandlerMapping
on the deprecation of path extension config options.as of 5.3, the path is resolved externally and obtained withServletRequestPathUtils.getCachedPathValue(ServletRequest)
; this method always returnsUrlPathHelper.defaultInstance
.as of 5.2.4. See class-level note inRequestMappingHandlerMapping
on the deprecation of path extension config options.as of 5.2.4. See deprecation note onRequestMappingHandlerMapping.setUseSuffixPatternMatch(boolean)
.as of 6.0, seePathPatternParser.setMatchOptionalTrailingSeparator(boolean)
as of 5.3, the path is resolved externally and obtained withServletRequestPathUtils.getCachedPathValue(ServletRequest)
as of 5.2.4. See class-level note inRequestMappingHandlerMapping
on the deprecation of path extension config options.as of 5.2.4. See deprecation note onRequestMappingHandlerMapping.setUseSuffixPatternMatch(boolean)
.as of 6.0 together withRequestMappingInfo.BuilderConfiguration.setTrailingSlashMatch(boolean)
as of 6.0 sinceModelAttributeMethodProcessor
now raises theMethodArgumentNotValidException
subclass instead.as of 5.3, the path is resolved externally and obtained withServletRequestPathUtils.getCachedPathValue(ServletRequest)
as of 5.3, the path is resolved externally and obtained withServletRequestPathUtils.getCachedPathValue(ServletRequest)
as of 5.3, the path is resolved externally and obtained withServletRequestPathUtils.getCachedPathValue(ServletRequest)
as of 5.2.4org.springframework.web.servlet.resource.ResourceHttpRequestHandler.initContentNegotiationStrategy()as of 5.2.4 this method returnsnull
, and if a subclass returns an actual instance, the instance is used only as a source of media type mappings, if it contains any. Please, useResourceHttpRequestHandler.setMediaTypes(Map)
instead, or if you need to change behavior, you can overrideResourceHttpRequestHandler.getMediaType(HttpServletRequest, Resource)
.as of 5.2.4 in favor of usingResourceHttpRequestHandler.setMediaTypes(Map)
with mappings possibly obtained fromContentNegotiationManager.getMediaTypeMappings()
.as of 6.0, with no direct replacementas of 6.0, with no direct replacementas of 6.0, with no direct replacementas of 6.0, with no direct replacementas of 6.0, with no direct replacementas of 6.0, with no direct replacementas of 6.0, with no direct replacementas of 6.0, with no direct replacementas of 6.0, with no direct replacementas of 6.0, with no direct replacementas of 6.0, with no direct replacementas of 6.0, with no direct replacementas of 6.0, with no direct replacementas of 6.0, with no direct replacementas of 4.2, since thelastModified
flag is effectively ignored, with a must-revalidate header only generated if explicitly configuredas of 4.2, in favor ofWebContentGenerator.getCacheControl()
as of 4.2, in favor ofWebContentGenerator.getCacheControl()
as of 4.2, in favor ofWebContentGenerator.getCacheControl()
as of 4.2, in favor ofWebContentGenerator.getCacheControl()
as of 4.2, in favor ofWebContentGenerator.setCacheControl(org.springframework.http.CacheControl)
as of 4.2, since going forward, the HTTP 1.1 cache-control header will be required, with the HTTP 1.0 headers disappearingas of 4.2, in favor ofWebContentGenerator.setCacheControl(org.springframework.http.CacheControl)
as of 4.2, since going forward, the HTTP 1.1 cache-control header will be required, with the HTTP 1.0 headers disappearingas of 6.0, in favor ofAbstractWebSocketClient.executeInternal(WebSocketHandler, HttpHeaders, URI, List, List, Map)
as of 6.0, in favor ofWebSocketClient.execute(WebSocketHandler, String, Object...)
as of 6.0, in favor ofWebSocketClient.execute(WebSocketHandler, WebSocketHttpHeaders, URI)
as of 6.0, in favor ofWebSocketStompClient.connectAsync(String, StompSessionHandler, Object...)
as of 6.0, in favor ofTransport.connectAsync(TransportRequest, WebSocketHandler)
as of 6.0 together withPathPatternParser.setMatchOptionalTrailingSeparator(boolean)
.transparent support for trailing slashes is deprecated as of 6.0 in favor of configuring explicit redirects through a proxy, Servlet/web filter, or a controller.as of 5.3 in favor of usingUrlPathHelper.resolveAndCacheLookupPath(HttpServletRequest)
andUrlPathHelper.getResolvedLookupPath(ServletRequest)
.
-
ConstructorDescriptionas of 6.0.12 in favor of the builderthis constructor has been superseded by
Handle(int, String, String, String, boolean)
.as of 6.0.11, in favor of an extraRootBeanDefinition.setTargetType(ResolvableType)
callsince 5.2 in favor of the factory methodAnnotationMetadata.introspect(Class)
since 5.2 in favor of the factory methodAnnotationMetadata.introspect(Class)
. UseMergedAnnotation.asMap
fromStandardAnnotationMetadata.getAnnotations()
rather thanAnnotatedTypeMetadata.getAnnotationAttributes(String)
ifnestedAnnotationsAsMap
isfalse
since 5.2 in favor ofStandardAnnotationMetadata
since 5.2 in favor of obtaining instances viaAnnotationMetadata
as of Spring Framework 5.2.23 in favor of invokingOperatorMatches(ConcurrentMap, int, int, SpelNodeImpl...)
with a shared pattern cache insteadas of 5.2, in favor ofJettyClientHttpConnector(HttpClient, JettyResourceFactory)
as of 5.1, in favor ofHttpMessageNotReadableException(String, HttpInputMessage)
as of 5.1, in favor ofHttpMessageNotReadableException(String, Throwable, HttpInputMessage)
since 6.0.8, in favor ofAbstractServerHttpRequest(HttpMethod, URI, String, MultiValueMap)
since 6.0.8, in favor ofAbstractServerHttpRequest(HttpMethod, URI, String, MultiValueMap)
as of 6.0, in favor onFixedDelayTask(Runnable, Duration, Duration)
as of 6.0, in favor onFixedRateTask(Runnable, Duration, Duration)
as of 6.0, in favor onIntervalTask(Runnable, Duration)
as of 6.0, in favor onIntervalTask(Runnable, Duration, Duration)
as of 5.3, in favor ofCronExpression.parse(String)
as of 5.3, in favor ofCronExpression.parse(String)
as of 6.0, in favor onPeriodicTrigger(Duration)
as of 6.0, in favor onPeriodicTrigger(Duration)
as of 6.0, in favor ofSimpleTriggerContext(Instant, Instant, Instant)
as of 5.2.5, in favor ofTransactionAspectSupport.setTransactionAttributes(Properties)
as of 5.2.5, in favor ofTransactionInterceptor(TransactionManager, TransactionAttributeSource)
as of 6.0.12 since JTA 1.1+ requires implicit rollback-only setting in case of an exception thrown inbeforeCompletion
, so the regularSpringJtaSynchronizationAdapter(TransactionSynchronization)
constructor is sufficient for all scenariosas of 6.0.12 since JTA 1.1+ requires implicit rollback-only setting in case of an exception thrown inbeforeCompletion
, so the regularSpringJtaSynchronizationAdapter(TransactionSynchronization)
constructor is sufficient for all scenariosas of 6.0as of 6.0as of 5.3.4 in favor usingRequestMappingInfo.Builder
viaRequestMappingInfo.paths(String...)
.as of 5.3.4 in favor usingRequestMappingInfo.Builder
viaRequestMappingInfo.paths(String...)
.since 5.3.4 in favor of using aRequestMappingInfo.Builder
viaRequestMappingInfo.mutate()
.as of 5.3.5 in favor ofHandshakeInfo(URI, HttpHeaders, MultiValueMap, Mono, String, InetSocketAddress, Map, String)
as of 5.3 in favor ofPatternsRequestCondition(String[], boolean, PathMatcher)
.as of 5.2.4. See class-level note inRequestMappingHandlerMapping
on the deprecation of path extension config options.as of 5.2.4. See class-level note inRequestMappingHandlerMapping
on the deprecation of path extension config options.as of 5.3 in favor usingRequestMappingInfo.Builder
viaRequestMappingInfo.paths(String...)
.as of 5.3 in favor usingRequestMappingInfo.Builder
viaRequestMappingInfo.paths(String...)
.since 5.3 in favor of usingRequestMappingInfo.addCustomCondition(RequestCondition)
.as of 6.0, in favor ofAbstractClientSockJsSession(TransportRequest, WebSocketHandler, CompletableFuture)
as of 6.0, in favor ofWebSocketClientSockJsSession(TransportRequest, WebSocketHandler, CompletableFuture)
as of 6.0, in favor ofXhrClientSockJsSession(TransportRequest, WebSocketHandler, XhrTransport, CompletableFuture)
-
Enum ConstantDescriptionin favor of
ClientHttpObservationDocumentation.LowCardinalityKeyNames.CLIENT_NAME
; scheduled for removal in 6.2. This will be available both as a low and high cardinality key value.in favor ofHttpStatus.EARLY_HINTS
which will be returned fromHttpStatus.valueOf(103)
in favor ofHttpStatus.FOUND
which will be returned fromHttpStatus.valueOf(302)
in favor ofHttpStatus.PAYLOAD_TOO_LARGE
which will be returned fromHttpStatus.valueOf(413)
in favor ofHttpStatus.URI_TOO_LONG
which will be returned fromHttpStatus.valueOf(414)
due to security concerns regarding in-band configuration of a proxyin favor ofClientHttpObservationDocumentation.LowCardinalityKeyNames.CLIENT_NAME
; scheduled for removal in 6.2. This will be available both as a low and high cardinality key value.