This commit also includes partial work to ensure framework works in full native/AOT mode.
Also, PollableBean remains and will simply not work in AOT mode until https://github.com/spring-projects/spring-framework/issues/28748 is resolved. That said, i will be deprecating t and it will be removed in the next release given that we already have configurable alternative
Resolves#2456
Update maven surefire-plugin to 3.0.0-M7 to address an issue
with how the newly added GlobalEmbeddedKafkaTestExecutionListener
in spring-kafka-test loads configuration parameters. The current
versions (2.x) of the plugin are not properly loading these parameters.
https://maven.apache.org/surefire/download.cgi
In Kafka Streams binder, we need to exclude the SendToDlqAndContinue
BiFunction by adding it to the ineligible function definitions.
See this commit for more context: 8ec15fa3ca
* Migrate Kafka Streams branching sample
* Cleanup some Kafka samples
* copyright header added to several files
* Spring Boot Maven plugin put into parent samples pom.xml
* Removed unused dependency and fixed title in README.adoc
When DLQ is enabled on a consumer binding, the internal producer properties
used by the DLQ mechanism to send to the topic is not populated with the
correct binding name. In the previous version, it was working fine since
we were relying on a ThreadLocal. This is revamped recently to properly
introduce a binding name as a top level property in ProducerProperties.
However, this was not set on the internal producer properties used by the
DLQ. This PR addresses this issue.
Resolves https://github.com/spring-cloud/spring-cloud-stream/issues/2417Resolves#2418
An internal helper method used by StreamBridge for resolving the
binder target type to attach the target binder protocol, does not
take into account the binder name when resolving the binder configuration.
Fixing this issue.
Resolves https://github.com/spring-cloud/spring-cloud-stream/issues/2379Resolves#2401
An internal helper method used by StreamBridge for resolving the
binder target type to attach the target binder protocol, does not
take into account the binder name when resolving the binder configuration.
Fixing this issue.
Resolves https://github.com/spring-cloud/spring-cloud-stream/issues/2379
* Make confluent-schema-registry-integration sample poms consistent
* Update <description> w/ "Confluent" prefix
* Put spring-cloud-dependencies back to 2022.0.0-SNAPSHOT (I got confused w 2021 for a minute)
* Pull deps up to base pom.xml
