Deprecated API

Contents

• For Removal
• Methods
• Constructors

For Removal

Element	Description
org.springframework.kafka.core.reactive.ReactiveKafkaProducerTemplate.flush()	- flush does not make sense in the context of a reactive flow since, the send completion signal is a send result, which implies that a flush is redundant. If you use this method with reactor-kafka 1.3 or later, it must be scheduled to avoid a deadlock; see https://issues.apache.org/jira/browse/KAFKA-10790

Methods

Method	Description
org.springframework.kafka.core.reactive.ReactiveKafkaProducerTemplate.flush()	- flush does not make sense in the context of a reactive flow since, the send completion signal is a send result, which implies that a flush is redundant. If you use this method with reactor-kafka 1.3 or later, it must be scheduled to avoid a deadlock; see https://issues.apache.org/jira/browse/KAFKA-10790
org.springframework.kafka.listener.AfterRollbackProcessor.process(List<ConsumerRecord<K, V>>, Consumer<K, V>, Exception, boolean)	in favor of AfterRollbackProcessor.process(List, Consumer, Exception, boolean, ContainerProperties.EOSMode).
org.springframework.kafka.listener.ContainerProperties.getConsumerStartTimout()
org.springframework.kafka.listener.ContainerProperties.setConsumerStartTimout(Duration)

Constructors

Constructor	Description
org.springframework.kafka.config.MultiMethodKafkaListenerEndpoint(List<Method>, Object)	in favor of MultiMethodKafkaListenerEndpoint(List, Method, Object).
org.springframework.kafka.listener.adapter.DelegatingInvocableHandler(List<InvocableHandlerMethod>, Object, BeanExpressionResolver, BeanExpressionContext)	in favor of DelegatingInvocableHandler(List, InvocableHandlerMethod, Object, BeanExpressionResolver, BeanExpressionContext, BeanFactory, Validator)