Out of curiosity, did anyone of you play around with supplying lambdas as beans? I’m talking about t...

# spring

[Philipp Mayer]

Out of curiosity, did anyone of you play around with supplying lambdas as beans?
I’m talking about the following:

@Configuration
class MyConfig {
    @Bean
    fun sendAnEmail(emailPublisher: EmailPubSubPublisher) = sendAnEmailLambdaVersion(emailPublisher)
}

fun sendAnEmailLambdaVersion(emailPublisher: EmailPubSubPublisher): (SomeEmail) -> Mono<String> =
    { email: SomeEmail -> emailPublisher.send(email) }

sure it works, but throwing @Bean on the function directly would be ofc more elegant, but I’m currently making no progress in that direction.
Does anyone have any experience with that? Thanks! 🙂

[Saharath Kleips]

We do this a lot for spring cloud streams, we would normally write this as:

@Bean
fun sendAnEmail(emailPublisher: ...): (SomeEmail) -> Mono<String> = { emailPublisher.send(it) }

[Philipp Mayer]

I’m really curious why Beans on functions is only integrated in spring cloud streams, but not in Spring Core. 🤔

[Saharath Kleips]

I believe it comes from spring-cloud-function-kotlin rather than streams

[Saharath Kleips]

Alternatively, I think using the Java interfaces work and then you can use SAM interfaces?

@Bean
fun sendAnEmail(emailPublisher: ...): Function<SomeEmail, MonoString> = Function { ... }

[Philipp Mayer]

Seems like I gotta dig more into that..