910f116332
* GH-276 Apply ComponentCustomizer in other modules Fixes https://github.com/spring-cloud/stream-applications/issues/276 Some changes are straightforward as just a `ComponentCustomizer<?>` injection and its optional usage for the target component customization. Other changes are more drastic since it is better to use `proxyBeanMethods = false`, so some direct bean method calls had to be reworked to the bean method argument injections * Fix some deprecations from Project Reactor * Remove `UpdatingMongoDbMessageSource` since `MongoDbMessageSource` supports now an `update` option in Spring Integration NOTE: The `ZeroMqSupplierConfiguration` has its own customizer already like `Consumer<ZMQ.Socket>`, so it can be revised to a more broader solution, but in the future version. Some modules just does not make sense to modify for more advance customization since all their configuration is covered with plain configuration properties. See `splitter-function` or `wavefront-consumer` * * Use `ObjectProvider<WebClientCustomizer>` for `HttpRequestFunctionConfiguration` instead of our own `ComponentCustomizer`. Although this has to be revised in favor of fully auto-configured `WebClient.Builder`. Even that `maximumBufferSize` is included into codecs configuration properties. * The `MongoDbMessageSource` has now an `update` option in Spring Integration therefore remove redundant already `UpdatingMongoDbMessageSource` and populate `this.properties.getUpdateExpression()` directly ot the `MongoDbMessageSource` bean * Modify supplier configurations to avoid manual starts for endpoints on reactive `Publisher` subscriptions. Spring Integration provides now a `toReactivePublisher(true)` operator to have all the endpoints stopped on start, but started automatically when subscription happens to the provided `Publisher` * Update Copyright to the current year for all the affected classes * Use `@Nullable` instead of `ObjectProvider` in the `AggregatorFunctionConfiguration` dependency injection for consistency * Fix `LogConsumerConfiguration` to not have a `log()` in the end - it is not terminal in Spring Integration anymore. Use recommended `nullChannel()` terminating operator for use-cases like this. * * Remove `beanName` from `ComponentCustomizer` contract Co-authored-by: Chris Bono <cbono@vmware.com>
# Aggregator Function This module provides an aggregation function that can be reused and composed in other applications. ## Beans for injection You can import the `AggregatorFunctionConfiguration` in a Spring Boot application and then inject the following bean. `aggregatorFunction` You can use `aggregatorFunction` as a qualifier when injecting. Once injected, you can use the `apply` method of the `Function` to invoke it and get the result. ## Configuration Options For more information on the various options available, please see link:src/main/java/org/springframework/cloud/fn/aggregator/AggregatorFunctionProperties.java[AggregatorFunctionProperties.java] ## Tests See this link:src/test/java/org/springframework/cloud/fn/aggregator/AggregatorFunctionApplicationTests.java[test suite] for examples of how this function is used. ## Other usage See this link:../../../applications/processor/aggregator-processor/README.adoc[README] where this function is used to create a Spring Cloud Stream application.