Sébastien Deleuze

I think what will come up from #29484 should be usable for user implementation as well, maybe you could comment on it to bring this need to the attention of...

+1 for allowing using the functional bean registration API with Spring Boot, even if I am not sure yet exactly where should be the entry point. For the record, [here](https://github.com/mix-it/mixit/blob/95257dc9d21b14fc8f90d9d631a967b3ff482c07/src/main/kotlin/mixit/Context.kt)...

While `BeanRegistry`/ `BeanRegistrar` like interfaces are maybe needed from Spring Framework to avoid exposing all `GenericApplicationContext` API, I tend to think it would be nice to avoid forcing `@Configuration` usage...

+1 for waiting post 2.0 for this, I am just adding a link to this [Spring Framework 5 functional bean declaration blog post](https://spring.io/blog/2017/08/01/spring-framework-5-kotlin-apis-the-functional-way#functional-bean-definitions-with-spring-rsquo-s-new-kotlin-dsl) in Kotlin with a `Consumer` style approach,...

FYI, I have [updated](https://github.com/spring-projects/spring-framework/commit/8b8a6766de01467c8b45b1b9664f0ab2d58f7c69) Kotlin functional bean definition DSL to implement `ApplicationContextInitializer` so with Spring Framework 5 + Boot 2.0 you should be able to declare your beans like that...

Since [SPR-13779](https://jira.spring.io/browse/SPR-13779) has returned to 5.x backlog, I have given a new try to Boot + functional bean registration and have created a [Boot 2.0 based branch of my `spring-kotlin-functional`...

I think https://github.com/tgirard12/spring-webflux-kotlin-dsl shows a very nice example of what could look like a functional WebFlux application written in Kotlin (not sure it apply to Java). It could give us...

@benjishults I have only found [this question](https://stackoverflow.com/questions/46798347/postconstruct-not-called-when-using-kotlin-beandefinitiondsl) that I have just answered. Please post your other question to StackOverflow and I will answer you there.

After more thoughts, I think `context.initializer.classes` + an `ApplicationContextInitializer` class is ok in Java, but in Kotlin it require too much ceremony given the fact the `bean { }` DSL...

I think you can already write: ``` fun main(args: Array) { runApplication(*args) { addInitializers( beans { bean() }) } } ``` The issue is that it won't be taken in...