You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Setting a Jpa transaction manager on the container is not really recommended; this is for a KafkaAwareTransactionManager, to properly manage Kafka transactions.
Yes, on reflection, it should only accept the narrower type; we can deprecate the old setter.
Deprecated ContainerProperties#transactionManager and add new properties ContainerProperties#kafkaTransactionManager type is KafkaAwareTransactionManager.
If change transactionManager type to KafkaAwareTransactionManager, old version KafkaMessageListenerContainer earlyRecordInterceptorandearlyRecordInterceptorwill invalid. For compatibility, add new propertieskafkaTransactionManager`.
Uh oh!
There was an error while loading. Please reload this page.
From #2775
Deprecated
ContainerProperties#transactionManager
and add new propertiesContainerProperties#kafkaTransactionManager
type isKafkaAwareTransactionManager
.If change transactionManager type to
KafkaAwareTransactionManager
, old versionKafkaMessageListenerContainer
earlyRecordInterceptorand
earlyRecordInterceptorwill invalid. For compatibility, add new properties
kafkaTransactionManager`.Other transaction manager can migration to
@Transactional
, see https://docs.spring.io/spring-kafka/reference/3.2/kafka/transactions.html#transaction-synchronization.The text was updated successfully, but these errors were encountered: