Thanks! Ill keep following this

By the way, how the function variant is different from just calling the queryForObject?

function variant is an extension function

looks interesting, but the first thing that came to mind was: how does it handle auth?

@dh44t just found that i used one of them :)

you're welcome

Has anyone looked at combining coroutines and Hystrix? With web-flux what would be the preferred method for the circuit breaker pattern?

Just found this: https://github.com/gothinkster/kotlin-spring-realworld-example-app @sdeleuze did you have a chance to review it?

@orangy Not yet but I will next week

@orangy On that topic any chance to get my PR https://github.com/JetBrains/kotlin-web-site/pull/783 and https://github.com/JetBrains/kotlin-examples/pull/49 merged ?

A lot of people start from these non idiomatic examples

Please ping @hhariri and/or @roman.belov on these.

Already done 😉

(at least Hadi, I will ping Roman)

Hi guys, I have this defined in my application class (Spring boot + Kotlin):

@Bean
    fun init(dataSource: DataSource) = CommandLineRunner {
     //Do things with DataSource
    }

Intellij gives me a warning: “Could not autowire. There is more than one bean of ‘DataSource’ type.” I’m trying to understand what to do about this. I’m particularly confused because of the following: 1) This compiles and runs correctly. 2) If I change the injection to constructor injection rather than injecting into the init function, the IDE stops giving warnings. 3) I have an import statement for DataSource defined, which I assumed would help resolve the ambiguity for the IDE.

import javax.sql.DataSource

Can someone shed some light on this please? I’m interested in knowing what I’m doing wrong, and how to avoid this problem. An explanation for why the warning isn’t given for constructor injection would also be appreciated.

regarding 2, that could be a difference in how the inspection works with Kotlin constructor, because you get the warning if you try injecting Datasource in Java

@User uploaded a file:

Thanks a lot, @jk !

That makes sense

Feedback wanted: as you may be aware, we introduced a few month ago function bean registration + Kotlin

ApplicationContext

extensions (see https://spring.io/blog/2017/01/04/introducing-kotlin-support-in-spring-framework-5-0#functional-bean-registration-with-kotlin). While the syntax is much shorter than in Java, I was still puzzled by the fact this way of declaring beans was not declarative, and would maybe be worth introducing a lightweight Kotlin DSL to get a 100% idomatic Kotlin syntax. I plan to introduce it as part of that pull request (https://github.com/spring-projects/spring-framework/pull/1473) that allows to declare your beans as following:

beans {
	bean<Foo>()
	bean<Bar>("bar")
	if (env.activeProfiles.contains("baz")) {
		bean { Baz(it.ref<Bar>()) }
		bean { Baz(it.ref("bar")) }
	}
}

Advantages compared to Regular

ApplicationContext

API are: - No exposure of low-level

ApplicationContext

API Focused DSL easier to read, but also easier to write with fewer entries in the auto-complete - Declarative syntax instead of functions with verbs like

registerBean

while still allowing programmatic registration of beans with if expressions or for loops - Such DSL is idiomatic in Kotlin - No need to have an

ApplicationContext

instance to write how you register your beans since

beans { }

DSL is conceptually a

Consumer<ApplicationContext>

Any feedbacks is welcome. Do you like such DSL? Are you ok with the syntax? Any issue to raise?

Definitely more idiomatic but the other way would be more familiar to people who've used the Java equivalent

I'd go with more idiomatic ☺️

Kotlin extensions will remain

I just would like to provide a more idiomatic DSL which does not exposed all the low-level

APplicationContext

API

@nekoinemo has left the channel

Any plans on adding

kobalt

as an option to

<http://start.spring.io|start.spring.io>

?

no disrespect intended, but a new language doesn’t need a new build tool

look at scala...